Doug Madory

@dougmadory@infosec.exchange
251 Followers
60 Following
284 Posts

Here’s the @Cloudflare write-up with a description of what caused the outage. It was caused by an internal error not a BGP hijack, but we already knew that.

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.

The Cloudflare Blog

Here’s the @Cloudflare write-up with a description of what caused the outage. It was caused by an internal error not a BGP hijack, but we already knew that.

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.

The Cloudflare Blog

Smart stuff from @jasonkoebler at @404mediaco:

“Using AI” is not a reporting strategy or a writing strategy, and it’s definitely not a business strategy.

The only journalism business strategy that works, and that will ever work in a sustainable way, is if you create something of value that people (human beings, not bots) want to read or watch or listen to, and that they cannot find anywhere else.

This can mean you’re breaking news, or it can mean that you have a particularly notable voice or personality. It can mean that you’re funny or irreverent or deeply serious or useful. It can mean that you confirm people’s priors in a way that makes them feel good. And you have to be trustworthy, to your audience at least. But basically, to make money doing journalism, you have to publish “content,” relatively often, that people want to consume. 

https://www.404media.co/the-medias-pivot-to-ai-is-not-real-and-not-going-to-work/

#AI #journalism

The Media's Pivot to AI Is Not Real and Not Going to Work

AI is not going to save media companies, and forcing journalists to use AI is not a business model.

404 Media
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: 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.

The Cloudflare Blog
Cloudflare DNS outage & BGP route hijack

Post covering hijack of 1.1.1.0/24 by AS4755

Personal blog of Anurag Bhatia
Also, the IPv6 route for Cloudflare's public DNS resolver (2606:4700:4700::/48) also went down at the same time as 1.1.1.0/24 and 1.0.0.0/24. It wasn't hijacked.
Also, the IPv6 route for Cloudflare's public DNS resolver (2606:4700:4700::/48) also went down at the same time as 1.1.1.0/24 and 1.0.0.0/24. It wasn't hijacked.

Just to clear up some misinfo circulating, a BGP hijack was not the cause of
Cloudflare DNS going down today.

At 21:51 UTC, Cloudflare (AS13335) withdrew both 1.1.1.0/24 and 1.0.0.0/24 for an unknown reason.

I suspect AS4755 was always announcing 1.1.1.0/24, when CF went away, it leaked a bit (i.e. "%2").

https://infosec.exchange/@GossiTheDog@cyberplace.social/114854023690856642

Infosec Exchange

Just to clear up some misinfo circulating, a BGP hijack was not the cause of
Cloudflare DNS going down today.

At 21:51 UTC, Cloudflare (AS13335) withdrew both 1.1.1.0/24 and 1.0.0.0/24 for an unknown reason.

I suspect AS4755 was always announcing 1.1.1.0/24, when CF went away, it leaked a bit (i.e. "%2").

https://infosec.exchange/@GossiTheDog@cyberplace.social/114854023690856642

Infosec Exchange

New entries in @Starlink's GeoIP file for #India appear the day after the country's space regulator granted a license to launch operations in India.

This was the final regulatory hurdle for the satellite provider to enter the massive South Asian market.

https://www.reuters.com/world/india/musks-starlink-receives-indias-final-regulatory-nod-launch-sources-say-2025-07-09/