Quote:
Originally Posted by Qtx
Yeah, makes perfect sense. I read two articles initially which said it was a DNS problem without mentioning any other issues, so didn't think any further than that.
The fact that BT wouldn't talk to the media or give them any information,(beside the fact it wasn't related to them playing with website blocking filters) you may be right about it being human error.
|
There aren't many other things that can cause a properly designed network to suddenly drop prefixes like this. Even if one router did fail the other one would be receiving the prefixes from the access edge, advertising them into the core and in turn the Internet facing routers advertising them onwards.
If primary and shadow both borked, or routes were getting nulled in the network someone screwed up. Friday is a good night to do changes, less interactive business traffic.
https://www.linkedin.com/in/neilmcrae can I'm sure advise
EDIT: A swift chat indicates that the issue was due to routing problems between 2 autonomous systems on the BT network. Various services including name, Cleanfeed, etc, are hosted in 5400, customer subnets including the one I'm using are hosted in 2856, and they stopped talking to each other, at one point there was a single route with those two systems in its path. Ooops.
route: 109.144.0.0/12
descr: BT Public Internet Service
origin: AS2856