Cloudflare logs and traces pricing changes on December 1, 2026: what the docs say

DHSeaDev — Chrome Extensions, Windows Tools, & Idle Games

Cloudflare Observability is the part of Cloudflare that stores and lets you search logs and traces, and starting December 1, 2026 it bills them by the gigabyte ingested and the gigabyte-month stored instead of by the number of events. Cloudflare announced the change on October 2, 2026 in its blog post introducing eight Observability updates, and its pricing documentation, last updated November 11, 2026, holds the current numbers. This post is a plain summary of what those pages say, read on November 20, 2026, with the places where sources disagree marked. The Ask AI desk on this site runs on a Cloudflare Worker, which I covered in the post about moving it, so I read the notice closely. I did not check any account usage for this post.

What changes on December 1, 2026?

One pricing model now covers logs and traces across Cloudflare, including existing Developer Platform logs for Workers, Containers and AI Gateway, plus all tracing data. Usage is measured in gigabytes because log and trace sizes vary a lot between applications. According to the documentation, Free, Pro and Business accounts move automatically on December 1, nothing is charged before that date, and ingestion is billed only for data received on or after it. Enterprise accounts keep their contract terms until renewal.

The notice email Cloudflare sent says accounts on the Workers Paid plan automatically receive an Observability Paid subscription, and accounts with no Workers Paid plan stay on Observability Free with no charges. The pricing page itself does not name Workers Paid, so check your own notice if that is your plan.

What do the Free and Paid plans include?

Cloudflare Observability allowances from December 1, 2026Free plan: 0.5 GB ingested per day, 7-day retention, no extra usage. Paid plan: 50 GB ingested and 10 GB-month stored per billing cycle, then 25 cents per extra GB ingested and 10 cents per extra GB-month stored.Free0.5 GB ingested per day7-day retentionNo extra usage availableIngestion pauses at the daily capPaid50 GB ingested per cycle10 GB-month stored per cycle$0.25 per extra GB ingested$0.10 per extra GB-month stored
Allowances from December 1, 2026, per the Cloudflare pricing documentation read on November 20, 2026.
PlanIncluded ingestionIncluded storageExtra usage
Free0.5 GB per day7 days of retentionNot available
Paid50 GB per billing cycle10 GB-month per billing cycle$0.25 per GB ingested, $0.10 per GB-month stored

Ingestion and storage are separate meters, so unused ingestion allowance cannot cover storage or the other way round, and allowances do not roll over between billing cycles. Paid usage continues past the allowance and is billed at those rates, and the page states no cap. Cloudflare says configurable retention of 30, 90 and 365 days is planned, with no date given.

One discrepancy to know about: an earlier copy of the pricing page that I retrieved showed 12 GB-month of included storage, while the page read twice on November 20 and the Cloudflare blog post both say 10. I use 10. Confirm against the live page before you plan around it.

Which products share the allowance?

Cloudflare Traces, Workers Logs, Workers Traces, Containers logs, R2 Data Access Logs, AI Gateway logs and Issues draw from one account-level ingestion allowance and one storage allowance. My reading is that one busy product can use up what the others were counting on.

How is usage measured?

Ingestion counts the size of each event as received, including the event body, the default enriched attributes and any custom attributes, measured before compression. Dropped events do not count, so sampling before data is stored lowers both meters. Storage is measured in GB-month: each day the maximum queryable data is recorded, the daily figures are added up, and the sum is divided by 30. With steady ingestion and the default seven-day retention, that works out to roughly the GB ingested times 7, divided by 30.

Cloudflare gives its own example. A Paid account that ingests 75 GB in a cycle has 17.5 GB-month of storage (75 x 7 / 30). Ingestion costs (75 – 50) x $0.25 = $6.25, storage costs (17.5 – 10) x $0.10 = $0.75, and the total is $7.00.

What happens when a Free account reaches the daily limit?

Cloudflare stops ingesting new data until the allowance resets at 00:00 UTC, and data already sent stays queryable until its seven-day retention ends. The documentation describes ingestion stopping, not requests failing. I read that as the application continuing to run with its logging paused, but the page does not say so in those words, so treat that as my inference.

How did Workers Logs pricing work before?

The Cloudflare Workers pricing page, as I retrieved it, listed Workers Logs on the Free plan at 200,000 log events per day with 3 days of retention, and on Paid at 20 million events a month included, then $0.60 per additional million, with 7 days of retention. That page may predate the change, so I give it as the old model and not as current terms. The old model counted events and the new one counts bytes. In my inference, a service that writes a few very large log lines is treated more harshly by the new model and a service that writes many tiny ones more kindly.

What else is priced separately?

Logpush exports get their own usage pricing: 25 GB a month included for exports to Cloudflare destinations, then $0.03 per GB; 25 GB for external destinations, then $0.10 per GB; and 1 GB of transformations, then $0.04 per GB. See the Logpush pricing page. OpenTelemetry destination usage stays on event-based pricing. Unsampled security datasets and legacy Log Explorer datasets cost $1 per GB ingested with 30 days of retention and do not use the shared allowances.

What can you do before December 1?

  • Read your notice email and confirm which plan your account is on. Paid accounts will be able to see ingestion, storage, remaining allowance and estimated charges in Billable Usage.
  • Sample your logs. The Workers Logs documentation shows a head sampling rate setting in the Worker observability configuration, for example 0.01 for one percent.
  • Turn off invocation logs you never read. The same documentation lists an invocation logs setting that can be set to false.
  • Log less per line. Custom attributes count toward ingestion, so large attributes cost more.

Related posts on this site: why the Ask AI proxy had to move off Val Town, how the Ask AI desk was first built and what Cloudflare Pages taught me about shipping games. You can try the Ask AI desk yourself. Sources read on November 20, 2026: Cloudflare Observability pricing, Cloudflare blog, 8 major updates to Observability (October 2, 2026), Logpush pricing, Workers pricing and Workers Logs.