Minor impactResolvedCDN

Cloudflare incident: Secondary DNS Update Delays

Cloudflare reported this minor-impact incident on its official status page on Sep 25, 2026, 10:10 UTC. It has since been resolved.

Right now Cloudflare is operational. Live Cloudflare status →

🔔 Get alerted when Cloudflare has issuesFree · email alerts · no credit card
Sep 25, 2026, 10:10 UTC
started
Sep 25, 2026, 01:52 UTC
resolved
—
duration
Minor
impact

Timeline

updates from Cloudflare's status page ↗
  1. resolvedSep 25, 2026, 01:52 UTC

    Cloudflare observed and resolved delays with Secondary DNS zone transfers. Customers may have experienced delays when record updates made on primary nameservers propagate to Cloudflare Secondary DNS as well as in the other direction. DNS resolution and edge proxying remain unaffected and continue to function normally. Impact on DNS transfers may have been observed today, from 00:05:10 UTC to 01:52:54.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cloudflare's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cloudflare have incidents?

Cloudflare reported 38 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 28m. See Cloudflare's uptime and incident history

← Previous: Edit Compression Rule Issue (Sep 25, 2026)Next: Cloudflare Cloud Access Security Broker (CASB) Issues (Sep 26, 2026) →
Cloudflare incident on Sep 25, 2026: Secondary DNS Update Delays · APIStatus.watch