Cloudflare 1.1.1.1 Incident on July 14, 2025 (blog.cloudflare.com)

Article summary

Cloudflare experienced a 62-minute outage of its 1.1.1.1 public DNS Resolver service on July 14, 2025, due to a misconfiguration of legacy systems. The outage was caused by a configuration error introduced during a release for a future Data Localization Suite service. The error was not immediately apparent and only became a problem when a subsequent configuration change was made. The incident affected users worldwide, with some traffic not returning to normal levels after the outage was resolved.

Main themes

• DNS outages
• anycast routing
• privacy concerns
• DNS diversity
• resilience and redundancy
• Cloudflare vs Google DNS

What commenters say

• Some users did not notice the outage because they use multiple DNS providers, such as Google DNS, which can serve as a fallback in case of failure.
• There are concerns about the privacy implications of using Google DNS, with some users preferring Cloudflare due to its stronger privacy policies.
• The use of anycast routing can lead to issues with DNS resolution, particularly if multiple services are dependent on the same anycast address.
• Having multiple DNS providers can help mitigate the risk of outages, but it may also introduce complexity and potential issues with DNS resolution.
• Some users prefer to use alternative DNS providers, such as Quad9, due to concerns about Cloudflare's handling of certain types of traffic.
• The incident highlights the importance of having a diverse and resilient DNS infrastructure to minimize the impact of outages.
• The use of DNS over Tor or other privacy-focused protocols can provide an additional layer of protection for users who are concerned about their online privacy.
• The centralization of DNS services can make them more vulnerable to outages and other disruptions, highlighting the need for greater diversity and resilience in the DNS ecosystem.