{"id":1,"date":"2025-12-15T18:29:22","date_gmt":"2025-12-15T18:29:22","guid":{"rendered":"http:\/\/localhost\/thedigitaldraft\/?p=1"},"modified":"2025-12-15T19:13:49","modified_gmt":"2025-12-15T19:13:49","slug":"cloudflare-1-1-1-1-dns-outage-july-2025","status":"publish","type":"post","link":"https:\/\/www.iamtiksha.com\/blog\/cloudflare-1-1-1-1-dns-outage-july-2025\/","title":{"rendered":"Cloudflare\u2019s 1.1.1.1 DNS Service Outage on July 14 – What Happened and Why"},"content":{"rendered":"\n

On July 14, 2025<\/strong>, many people around the world suddenly found that they couldn\u2019t access websites or use the internet normally. The reason? A temporary issue with Cloudflare\u2019s free DNS service<\/strong>, called 1.1.1.1<\/strong>.<\/p>\n\n\n\n

The outage started at 21:52 UTC<\/strong> and lasted about an hour, ending at 22:54 UTC<\/strong>. During that time, most users who rely on 1.1.1.1 for faster and safer browsing were affected.<\/p>\n\n\n\n

What Is 1.1.1.1?<\/h3>\n\n\n\n

Think of 1.1.1.1 as a phonebook for the internet. When you type a website like google.com<\/code>, your device asks a DNS server like 1.1.1.1, \u201cWhat\u2019s the IP address for this website?\u201d If the DNS server isn\u2019t working, your device doesn\u2019t know where to go\u2014so websites just won\u2019t load.<\/p>\n\n\n\n

Cloudflare has offered the 1.1.1.1 service since 2018. It’s free<\/strong>, fast<\/strong>, and private<\/strong>, and millions of people around the world use it every day.<\/p>\n\n\n\n

Why Did 1.1.1.1 Stop Working?<\/h2>\n\n\n\n

The problem was caused by an internal mistake<\/strong>, not a hack or cyberattack.<\/p>\n\n\n\n

Cloudflare was updating part of their system to prepare for a new service. While doing this, they accidentally included 1.1.1.1\u2019s address in a section of the system where it didn\u2019t belong. Nothing broke at that time, so they didn\u2019t notice anything wrong.<\/p>\n\n\n\n

But on July 14<\/strong>, they made another update that triggered a global refresh of settings. That\u2019s when things went wrong: 1.1.1.1 was suddenly treated as if it was part of a new, inactive service. As a result, many of Cloudflare\u2019s servers around the world stopped offering the 1.1.1.1 DNS service.<\/p>\n\n\n\n

What Was the Impact?<\/h2>\n\n\n\n
    \n
  • Millions of users<\/strong>\u00a0around the world couldn\u2019t load websites because 1.1.1.1 wasn\u2019t responding.<\/li>\n\n\n\n
  • The problem lasted about\u00a01 hour<\/strong>.<\/li>\n\n\n\n
  • Some users were not affected if they used DNS over HTTPS (DoH) with\u00a0cloudflare-dns.com<\/code>, since it uses a different system.<\/li>\n\n\n\n
  • Cloudflare detected the issue, declared it an incident, and started fixing it right away.<\/li>\n<\/ul>\n\n\n\n

    How Did Cloudflare Fix It?<\/h2>\n\n\n\n

    At 22:20 UTC<\/strong>, they began undoing the bad configuration. This fix helped most of the servers get back online quickly. But about 23%<\/strong> of their servers needed extra time to reset, which is part of their normal safety process to avoid causing other problems.<\/p>\n\n\n\n

    By 22:54 UTC<\/strong>, the DNS service was fully restored around the world.<\/p>\n","protected":false},"excerpt":{"rendered":"

    On July 14, 2025, many people around the world suddenly found that they couldn\u2019t access websites or use the internet normally. The reason? A temporary issue with Cloudflare\u2019s free DNS service, called 1.1.1.1. The outage started at 21:52 UTC and lasted about an hour, ending at 22:54 UTC. During that time, most users who rely on 1.1.1.1 for faster and safer…<\/p>\n","protected":false},"author":1,"featured_media":17,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[18,25,16,23,24,15,22,26,20,21,17,19],"class_list":["post-1","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-development","tag-1-1-1-1","tag-beginner-tech-guide","tag-cloudflare","tag-cloudflare-dns","tag-dns-explained","tag-dns-outage","tag-internet-issues","tag-internet-outage","tag-july-2025","tag-networking","tag-tech-news","tag-website-down"],"_links":{"self":[{"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/posts\/1","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/comments?post=1"}],"version-history":[{"count":2,"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/posts\/1\/revisions"}],"predecessor-version":[{"id":18,"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/posts\/1\/revisions\/18"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/media\/17"}],"wp:attachment":[{"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/media?parent=1"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/categories?post=1"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.iamtiksha.com\/blog\/wp-json\/wp\/v2\/tags?post=1"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}