Alex KretzschmarCloudflare oopsie just now
Xe 
@ironicbadger that is a wild graph lol
furicle@ironicbadger
Not their issue as I understand it
https://cyberplace.social/@GossiTheDog/114854022522468162
Not their issue as I understand it
https://cyberplace.social/@GossiTheDog/114854022522468162
Kevin Beaumont (@[email protected])
Attached: 1 image If you’re wondering why half the internet broke tonight for a short period, TCS accidentally hijacked Cloudflare.HT @[email protected]
Brad@ironicbadger Is that a Cacti graph? I haven’t used that in almost a decade!
@burkettlabs smokeping
Alexander S@ironicbadger seems like a bad change deployment https://blog.cloudflare.com/cloudflare-1-1-1-1-incident-on-july-14-2025/
Cloudflare 1.1.1.1 Incident on July 14, 2025
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.