>"We are making the following changes: Introduce a maximum-prefix limit on our backbone BGP sessions - this would have shut down the backbone in Atlanta, but o

>"We are making the following changes: Introduce a maximum-prefix limit on our backbone BGP sessions - this would have shut down the backbone in Atlanta, but our network is built to function properly without a backbone. This change will be deployed on Monday, July 20. Change the BGP local-preference for local server routes. This change will prevent a single location from attracting other locations’ traffic in a similar manner. This change has been deployed following the incident." It should be noted that configuring prefix limits for your BGP peers is kind of BGP 101. It's mentioned in every "BGP Best Practices" type document.[1] It's there for exactly this purpose to prevent router meltdown and resource exhaustion. For a company who blows their horn as much as these folks seem to about their network this is embarrassing. I think it's worth mentioning that it was this time last year when Verizon bungled their own BGP configuration and brought down parts of the internet. When that incident occurred Cloudflare's CEO was front and center excoriating them for accepting routes without basic filtering [2]. This is exact same class of misconfiguration that befell them yesterday. [1] https://team-cymru.com/community-services/templates/secure-bgp-template/ https://team-cymru.com/community-services/templates/secure-b... [2] https://twitter.com/eastdakota/status/1143182575680143361?lang=en https://twitter.com/eastdakota/status/1143182575680143361?la...