Cloudflare incident on August 21, 2025
blog.cloudflare.com
Cloudflare incident on August 21, 2025
1–10 of 46 posts
Re: Cloudflare incident on August 21, 2025
#2Re: Cloudflare incident on August 21, 2025
#3Re: Cloudflare incident on August 21, 2025
#4Re: Cloudflare incident on August 21, 2025
#5Re: Cloudflare incident on August 21, 2025
#6Re: Cloudflare incident on August 21, 2025
#7Wild that one tenant’s cache-hit traffic could tip over Cloudflare’s interconnect capacity
10Gbps is old technology now and any real ISP can probably afford 40 or 100 - for hundreds of dollars per link. But they're going to deploy that on their most utilized links first, and only if their peering partner can also afford it and exchanges enough traffic to justify it. So the smallest connections are typically going to be 10. (Lower than 10 is too small to justify a point-to-point peering at all).
If you have 10Gbps fiber at home, you could congest one of these links all by yourself.
Now this is Cloudflare talking to aws-east-1, so they should have shitloads of capacity there, probably at least 8x100 or more. But considering that AWS is the kind of environment where you can spin up 800 servers for a few hours to perform a massively parallel task, it's not surprising that someone did eventually create 800Gbps of traffic to the same place, or however much they have. Actually it's surprising it doesn't happen more often. Perhaps that's because AWS charges an arm and a leg for data transfer - 800Gbps is $5-$9 per second.
Re: Cloudflare incident on August 21, 2025
#8Re: Cloudflare incident on August 21, 2025
#9Re: Cloudflare incident on August 21, 2025
#10Anyone want to tell Cloudflare that BGP advertisements at AWS are automated and their congested network directly cause BGP withdrawals as the automated system detected congestion and decreased traffic to remediate it?
I think the withdrawal approach by AWS would normally work, as this action should desaturate the connections. Just really unfortunate that this caused routing through a link that was at half capacity.