Doug Madory

@dougmadory@infosec.exchange
255 Followers
61 Following
284 Posts
Internet analysis at Kentik
LinkedInhttps://www.linkedin.com/in/dougmadory/
Blog postshttps://www.kentik.com/blog/author/doug-madory/
Wikipediahttps://en.wikipedia.org/wiki/Doug_Madory
Twitterhttps://twitter.com/DougMadory
Doug Madory2d ago
Show threadDoug Madory2d ago

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
Show threadDoug Madory2d ago

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
Doug Madory2d ago
Jeri Dansky2d ago

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
Doug Madory2d ago
Cloudflare2d ago
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
Doug Madory2d ago
Anurag Bhatia2d ago

Checkout my blog post on 1.1.1.0/24 hijack by AS4755 - https://anuragbhatia.com/post/2025/07/cloudflare-dns-outage/

#Cloudflare #AS13335 #AS4755 #AS6453

Cloudflare DNS outage & BGP route hijack

Post covering hijack of 1.1.1.0/24 by AS4755

Personal blog of Anurag Bhatia
Show threadDoug Madory2d ago
@anurag great write up Anurag!
Show threadDoug Madory2d ago
@jtk we’ll have to read their blog post, which should be out any minute now. 😁
Show threadDoug Madory2d ago

@albonycal @GossiTheDog @ssamulczyk

As far as I can tell, Kevin’s shtick is to scan for security-related topics on social media, post about them as if he has some expertise on the matter and build up a following of people who think he’s some sort of security expert.

He’s not too concerned whether he’s correct. Social media rewards his noise. Seems to work for him, but, damn, it’s pretty pathetic.

Show threadDoug Madory2d ago
@jtk or is there a scenario where 4755 prioritized 1.1.1.0/24 from 13335 over its own static version? Then when 13335 withdrew it, it reverted to the internal route and advertised it externally.
Show threadDoug Madory2d ago
@jtk yeah it might not have been seen. Does RIPE have collectors downstream of 4755? If not, then they wouldn’t see it as 6453 would probably accept the route from 13335.