On October 2, Cloudflare announced eight updates bringing logs, traces, analytics, alerts, dashboards and export under its Observability platform.
A unified interface does not mean every feature is generally available. Cloudflare Traces is in open beta, while the unified SQL API and custom alerts are also in beta. Queries across multiple datasets remain a planned feature.
The pricing change is scheduled for December 1, 2026. Rather than counting events, it meters the volume ingested and stored separately. Cloudflare says Enterprise contracts will adopt it on renewal.
Why 10 and 12 GB-month produce different bills
The Paid plan includes 50 GB of ingestion per billing cycle. Additional ingestion is listed at USD 0.25 per GB and storage at USD 0.10 per GB-month. GB-month sums each day's maximum queryable storage and divides the total by 30.
The included storage allowance differs between sources. Cloudflare's October 2 announcement lists 10 GB-month, while an accessible pricing document lists 12 GB-month. These sources do not establish which allowance will be used for a particular account's bill.
The documentation's example of 75 GB ingested and 20 GB-month stored yields USD 7.05 in overages under a 12 GB-month inclusion. At a 10 GB-month inclusion, the same usage would yield USD 7.25. Both are calculations from published rates, not measured bills.
The default retention for logs and traces is seven days. Retention of 30, 90 or 365 days is described as upcoming and should not be confused with 30 days of domain analytics. Ingestion and storage allowances cannot be exchanged or carried into the next billing cycle.
Checking beta features separately from billing
One practical check is to verify query and alert availability against a particular dataset. A shared user interface does not prove that all feature paths have launched.
Because the storage allowance differs between documents, the pricing shown in the relevant account and contract needs checking at adoption time. No account-specific usage or bill was examined for this article.
Cloudflare Observability should be evaluated by each feature's rollout state and separate ingestion and storage charges, not by the unified interface alone.