Cloudflare Outage Blamed on Misconfig, Not BGP Hijack

Cloudflare confirmed that a recent disruption to its 1.1.1.1 DNS resolver on July 14 was not caused by a cyberattack but by a misconfiguration. The Cloudflare outage, blamed initially on a BGP hijack, lasted 62 minutes and affected millions of users globally. Engineers traced the issue to a dormant update from June 6 that mistakenly included production DNS prefixes in a test configuration.

The service became unreachable when a subsequent change triggered a global refresh, withdrawing DNS prefixes from all data centers. The Cloudflare outage, blamed again during analysis on a suspicious routing event, coincided with Tata Communications India (AS4755) announcing the 1.1.1.0/24 prefix. However, Cloudflare confirmed that the routing event did not cause the outage.

Engineers restored 77% of traffic within 30 minutes by reverting changes. Full service resumed at 22:54 UTC. The company plans to retire legacy systems and improve deployment safeguards.

Read the full article at

Cloudflare Confirms Recent 1.1.1.1 DNS Outage Caused by BGP Attack or Hijack