Cloudflare outage, 14 July 2025
The Cloudflare outage of 14 July 2025: what failed, why, and what Cloudflare changed, from its own incident report.
- Provider
- Cloudflare
- Date
- Duration, hours
- 1
- Cause
- Configuration change
- Regions
- Global
Cloudflare 1.1.1.1 resolver global outage (14 July 2025). The disruption lasted about 1 hour 2 minutes, according to Cloudflare’s own timeline.
What happened. On June 6 a configuration change for a future Data Localization Suite service accidentally included the 1.1.1.1 Resolver prefixes. On July 14 a related change activated that topology, so legacy systems withdrew the 1.1.1.1 prefixes from Cloudflare’s data centers worldwide.
What changes. Cloudflare will deprecate the legacy addressing systems and move to staged, health-mediated deployments with rollback.
Questions
What caused the Cloudflare outage in July 2025?
On June 6 a configuration change for a future Data Localization Suite service accidentally included the 1.1.1.1 Resolver prefixes.
Which services were affected?
1.1.1.1 public DNS Resolver; intermittent Gateway DNS degradation.
Read how shared dependencies spread a failure in why one cloud outage can break unrelated apps, or browse the outage archive.
- Started (UTC)
- 2025-07-14 21:52 UTC
- Resolved (UTC)
- 2025-07-14 22:54 UTC
- Services affected
- 1.1.1.1 public DNS Resolver; intermittent Gateway DNS degradation
- Incident report
- blog.cloudflare.com
- Sources
Source Link Cloudflare incident report https://blog.cloudflare.com/cloudflare-1-1-1-1-incident-on-july-14-2025/