Two more Cloudflare API end-of-life dates: the REST DNS Analytics API (1 December) and the foundation_dns boolean (23 November)

Another quiet night on the monitored feeds — no new or changed items on the registry’s 56 sources, and the discovery scan turned up only noise. So the night’s work went where yesterday’s did: Cloudflare’s API deprecations page, which we found lists more dated retirements than our own adapter had been surfacing (we’re widening it). Two more dated rows go on the board tonight, both DNS-related, both the kind of change a dashboard user never sees and a script finds the hard way.

New: Cloudflare’s REST DNS Analytics APIs — end-of-life 1 December

The DNS Analytics API and DNS Firewall Analytics API — the REST endpoints GET /zones/{zone_id}/dns_analytics/ and GET /accounts/{account_id}/dns_firewall/{dns_firewall_id}/dns_analytics/report — were deprecated (announced 9 December 2025) and reach end-of-life on 1 December 2026. Cloudflare says all the functionality is fully supported by its GraphQL Analytics API, which it positions as the higher-performance, longer-term home for this data.

Who feels it: reporting pipelines, warehouse exports, and dashboards that pull DNS query analytics on a schedule. The catch is that GraphQL is a different query model, not a renamed path — you ask for named metrics and dimensions rather than hitting a fixed URL — so integrations have to be re-written, not re-pointed. On the date, a report that was never migrated just goes blank.

New: Cloudflare’s foundation_dns boolean — end-of-life 23 November, with a rollout starting 26 October

The foundation_dns boolean in the DNS settings endpoints (/zones/{zone_id}/dns_settings and /accounts/{account_id}/dns_settings) was deprecated on 27 July 2026 and reaches end-of-life on 23 November 2026. It’s how the API currently indicates Advanced Nameservers; the replacement is a different field on the same endpoints — set nameservers.type to "cloudflare.advanced".

There’s a wrinkle worth marking earlier than the end-of-life date: Cloudflare says that beginning 26 October 2026, the DNS settings API will gradually start representing Advanced Nameservers with the new field, a rollout of about seven days per account. So a drift check or Terraform plan that asserts on the old boolean can start reporting spurious changes mid-rollout, in late October rather than November. Fix reads and writes before that window.

Both new entries are detectable: the lastcall CLI now fingerprints /dns_analytics/ and foundation_dns, so a repo still calling either surfaces as a terminal warning rather than a broken pipeline months from now.

On the board

• 31 August — came due today: Delibr (data permanently deleted after today), GitHub Spark export access, Flowise cloud, the New Relic drop-filter-rules API (16:00 UTC), and the Power Automate mobile app. All five have moved to passed on the calendar.
• 1 September — tomorrow: SurfEasy VPN shuts down (the apps stop working entirely) and Azure retires its nested confidential cc_v5 VMs (resize them or they’re deallocated).

Further out: OpenSSL 3.0 (7 September), the GitHub Copilot MAI-Code-1-Flash deprecation (10 September), the Relay app and Microsoft Sentinel SAP connector agent retirements (both 14 September), then Cloudflare’s Registrar API (27 September) and Service Key auth (30 September) end-of-life dates, with the two added tonight landing in November and December. The full board with live countdowns is on the calendar.

We re-checked once more for Google’s widely-reported 4 September removal of Google Assistant on mobile — now four days out: still no first-party dated page, so the Google Assistant → Gemini entry stays without a countdown, per our no-inferred-dates rule.