API
Cloudflare
The REST DNS Analytics API (/zones/{zone_id}/dns_analytics/) and DNS Firewall Analytics API (/accounts/{account_id}/dns_firewall/{id}/dns_analytics/report) stop working; analytics automation must move to Cloudflare's GraphQL Analytics API
departs 1 Dec 2026
Quick answers
- Is it true that Cloudflare retires the REST DNS Analytics API and DNS Firewall Analytics API — end-of-life 1 December 2026, move to the GraphQL Analytics API?
- Yes. Cloudflare has officially announced it, effective 1 Dec 2026. This affects anything that pulls DNS query analytics from Cloudflare through the old REST endpoints — dashboards, capacity and traffic reports, anomaly alerting, and any scheduled job that reads DNS or DNS Firewall analytics by calling /zones/{zone_id}/dns_analytics/ or /accounts/{account_id}/dns_firewall/{dns_firewall_id}/dns_analytics/report.
- When does it take effect?
- 1 Dec 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Migrate any integration that reads DNS or DNS Firewall analytics from the REST endpoints to Cloudflare's GraphQL Analytics API before 1 December 2026.
What this means for you
This affects anything that pulls DNS query analytics from Cloudflare through the old REST endpoints — dashboards, capacity and traffic reports, anomaly alerting, and any scheduled job that reads DNS or DNS Firewall analytics by calling /zones/{zone_id}/dns_analytics/ or /accounts/{account_id}/dns_firewall/{dns_firewall_id}/dns_analytics/report. On Cloudflare's own deprecations page, both REST APIs are listed as deprecated (announced 9 December 2025) and reaching end-of-life on 1 December 2026, after which requests to them are no longer supported. The analytics themselves are not going away: Cloudflare says all existing functionality is fully supported by its GraphQL Analytics API, which it positions as the higher-performance, longer-term home for this data. As with Cloudflare's other endpoint retirements, the sharp edge is unattended automation rather than interactive use — someone reading graphs in the dashboard notices nothing, but a reporting pipeline that queries the REST path on a schedule will start failing on the date. The move is more than a URL swap: GraphQL uses a different query model, so integrations need to be re-written, not just re-pointed.
Where to go
Migrate any integration that reads DNS or DNS Firewall analytics from the REST endpoints to Cloudflare's GraphQL Analytics API before 1 December 2026. Because GraphQL is a different query shape rather than a drop-in path rename, budget real work: identify the metrics and dimensions your current reports use, express them as GraphQL queries against the DNS analytics datasets, and update the code, credentials, and any scheduled jobs or dashboards that consume the output. Cloudflare links the GraphQL replacements for both the DNS Analytics API and the DNS Firewall Analytics API from the same deprecations page. Do the cut-over before the date so a report does not silently go blank.
- Cloudflare's GraphQL Analytics API for DNS analytics (developers.cloudflare.com/analytics/graphql-api/) — the named replacement for both REST endpoints
Cloudflare has set an end-of-life date for the REST APIs that return DNS query analytics. On its API deprecations page, the company lists the DNS Analytics API and the DNS Firewall Analytics API as deprecated — announced 9 December 2025 — and reaching end-of-life on 1 December 2026. After that date, requests to the old REST paths are no longer supported.
The two endpoints being retired are GET /zones/{zone_id}/dns_analytics/ (DNS Analytics) and GET /accounts/{account_id}/dns_firewall/{dns_firewall_id}/dns_analytics/report (DNS Firewall Analytics). Cloudflare is clear that the data is not disappearing: it says all existing functionality is fully supported by its GraphQL Analytics API, which it describes as offering improved performance, flexibility, and long-term support.
As with the rest of Cloudflare’s scheduled endpoint retirements, the risk sits in automation, not in the dashboard. Someone reading traffic graphs in the Cloudflare UI sees nothing change. What breaks is anything that reads DNS analytics on a schedule by calling the REST path directly — traffic and capacity reports, exports into a data warehouse, anomaly alerting, and bespoke dashboards. On 1 December 2026 those calls start returning errors, and the failure shows up as a report that quietly goes blank rather than a warning ahead of time.
The catch is that this is not a path rename. GraphQL uses a different query model — you ask for named metrics and dimensions rather than hitting a fixed URL — so an integration has to be re-written, not re-pointed. Map the metrics your current reports use to the equivalent GraphQL datasets, rebuild the queries, and update the jobs and dashboards that consume them, all before 1 December 2026.
This is one of a cluster of end-of-life dates Cloudflare has scheduled on the same page, several of them for REST endpoints being replaced by newer APIs. If you drive Cloudflare through its API, it is worth reading the whole page rather than just this row.
Entry changelog
- — last reviewed.
- — Entry created from Cloudflare's official API deprecations page (developers.cloudflare.com/fundamentals/api/reference/deprecations). The deprecation (announced 9 December 2025), the 1 December 2026 end-of-life date, the two affected REST paths (/zones/{zone_id}/dns_analytics/ and /accounts/{account_id}/dns_firewall/{dns_firewall_id}/dns_analytics/report), and the GraphQL Analytics API replacement are all quoted from that page. Added a detect: fingerprint (text:/dns_analytics) so the lastcall CLI flags code still calling the legacy REST analytics paths.
Put this countdown in your README
Building on Cloudflare? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/cloudflare-dns-analytics-api-eol)Spot an error or a changed date? Tell us and it’s corrected the same night.