Earlier quoted context omitted.
Thanks for the updates. I wish I could get this information somewhere other than hacker news though. :(
The team is updating the status page but not with granular detail because they'd have to spend time discussing what to say. I'm giving you the blow by blow.
Route Leak Impacting Cloudflare
31–40 of 164 posts
Re: Route Leak Impacting Cloudflare
#32How would that kind of disruption happen? Someone else also anycasting the CF IP addresses?
On that protocol, the various systems broadcast what prefixes they can route, which then affects the rest of the networks' routing decisions.
By error or malice, a system can report a prefix they cannot or should not route, causing other systems to start routing traffic across it. This will either just cause weird routes (such as ones going through certain suspicious countries), cause poor performance for those routed, or no connection at all for those routed.
Re: Route Leak Impacting Cloudflare
#33Isn't HN on Cloudflare? How are we reading about a CF outage on a site that runs behind CF?
Re: Route Leak Impacting Cloudflare
#34How would that kind of disruption happen? Someone else also anycasting the CF IP addresses?
Re: Route Leak Impacting Cloudflare
#35Re: Route Leak Impacting Cloudflare
#36Re: Route Leak Impacting Cloudflare
#37Does anyone know which global sites were or still are unavailable because of Cloudflare crash? Maybe some media sites?
Re: Route Leak Impacting Cloudflare
#38Re: Route Leak Impacting Cloudflare
#39How would that kind of disruption happen? Someone else also anycasting the CF IP addresses?
BGP route/prefix leaks. BGP is the protocol that deals with routing across the various internet backbones (known in the protocol as "autonomous systems", identified by an AS number). On that protocol, the various systems broadcast what prefixes they can route, which then affects the rest of the networks' routing decisions. By error or malice, a system can report a prefix they cannot or should not route, causing other…
Re: Route Leak Impacting Cloudflare
#40Disabling HTTP proxy and leaving "DNS only" option in CloudFlare DNS settings solved the problem for us.