// AI Platform Drift

Cloudflare Logpush adds account-scoped HTTP request logs

Cloudflare developer changelog · published 2026-10-27 18:04 UTC
WORTH KNOWING VERIFY_ONLY API
WHAT CHANGEDCloudflare Logpush now supports HTTP request logs as an account-scoped dataset, effective 21 October 2026. Previously, each zone required a separate Logpush job; now one account-level job can deliver logs for all zones in an account. The ZoneName field identifies the source zone in each log entry. Custom fields remain configured per zone.
WHY IT MATTERSIf you run Logpush jobs for multiple Cloudflare zones, you can consolidate to a single account-level job instead of maintaining separate jobs per zone. This reduces operational overhead for multi-zone accounts. Existing zone-scoped jobs continue to work; this is an additional option, not a replacement.
WHAT TO DOIf you maintain Logpush jobs for multiple zones in the same Cloudflare account, evaluate whether consolidating to one account-scoped job simplifies your setup. Check the API configuration documentation for account-level job creation steps.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## logpush, Logs - Account-scoped HTTP request logs in Logpush
+https://developers.cloudflare.com/changelog/post/2026-10-21-account-scoped-http-requests/
+Wed, 21 Oct 2026 00:00:00 GMT
+
+Cloudflare Logpush now supports HTTP request logs as an account-scoped dataset. Use one job to deliver logs for every zone in an account instead of maintaining a separate job for each zone.
+Create the job at the account level in the Cloudflare dashboard or through the Logpush API. The ZoneName field identifies the source zone in each log entry.
+Custom fields remain configured per zone. An account-scoped job honors the custom fields configuration for each zone but does not support account-wide custom fields configuration.
+For setup details, refer to API configuration.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew account-scoped Logpush capability changes how teams configure and manage HTTP request logging across zones.
signalsnew feature announcement · API capability expansion · deployment model change (zone-scoped to account-scoped) · operational workflow change (one job vs. multiple jobs) · future date (2026-10-21) · authentication/integration scope change
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)