On July 14th, 2025, Cloudflare made a change to our service topologies that caused an outage for 1.1.1.1 on the edge, resulting in downtime for 62 minutes for customers using the 1.1.1.1 public DNS Resolver as well as intermittent degradation of service for Gateway DNS.

We’re deeply sorry for this outage.

This outage was the result of an internal configuration error and not the result of an attack or a BGP hijack. In this blog post, we’re going to talk about what the failure was, why it occurred, and what we’re doing to make sure this doesn’t happen again.

Cloudflare's platform is a leading provider of internet security and performance solutions, offering insights into web security, content delivery, and DNS management. Through documentation, blog posts, and webinars, Cloudflare provides insights into protecting websites and applications from cyber threats and improving performance. Developers and IT professionals can learn about CDN (Content Delivery Network), DDoS mitigation, and firewall configurations to secure and accelerate web traffic.

Cloudflare

Cloudflare's 1.1.1.1 DNS resolver experienced a 62-minute global outage on July 14, 2025, caused by an internal configuration error that inadvertently linked the resolver's IP prefixes to a non-production Data Localization Suite service. The issue originated from a dormant misconfiguration made on June 6, which was triggered when changes were made to the test service on July 14, causing BGP route withdrawals globally. The outage affected most DNS resolution methods except DNS-over-HTTPS traffic using the cloudflare-dns.com domain. Cloudflare is addressing the root cause by deprecating legacy systems and implementing staged deployment methodologies.

Cloudflare 1.1.1.1 Incident on July 14, 2025

Technical description of the error and how it happened