Quote:
Originally Posted by Qtx
If DNS goes down, bandwidth goes down too as people don't load up their web pages. Still, the graph is BGP router availability rather than bandwidth but this is how bgmonitor tweeted it, which is probably why I read the graph a different way. The link to the tweet was in my previous post but i'll post it below anyway:
|
It's not router availability it's prefixes being advertised from the AS. Doesn't mean a router went down but that it stopped advertising some prefixes, hence my BT line lost its return path as it was no longer being advertised outside AS2856.
Actually it seemed to stop being advertised internally too. I suspect fat fingers when a configuration change was made to a route reflector; a single router going unavailable shouldn't cause this, there are almost certainly primary and shadow reflectors on the network.
DNS servers per se didn't go down, this was actually a routing issue on the BT network a side effect of which was that DNS became unavailable.
I do not use BT's DNS and had to admin down my Infinity line as both default gateway and the site I use for IP SLA were available
You misread the graph, it happens, no need to worry
---------- Post added at 12:51 ---------- Previous post was at 12:43 ----------
Quote:
Originally Posted by Qtx
The lack of info from BT has been pretty bad, just a general statement from a PR guy.
Seen a lot of people saying it was mostly major sites, such as amazon, twitter, facebook, netflix etc which seemed to all have problems while others were ok. Wondering if these sites were just noticed more as they are popular or if it was some kind of routing they do for particular sites.
|
Just noticed more. Everything from those to Deviantart to CNN were hosed, only the first 5 hops are common throughout.
Tracerting
www.twitter.com[199.16.156.38] ,Maximum hops:30
1 5ms 5ms 5ms 217.32.143.234
2 5ms 5ms 13ms 217.32.144.30
3 13ms 8ms 7ms 213.120.181.214
4 7ms 7ms 7ms 213.120.180.167
5 8ms 9ms 8ms 217.41.169.107
6 6ms 7ms 7ms 109.159.251.121
...
< Completed >
Tracerting
www.amazon.co.uk[178.236.7.220] ,Maximum hops:30
1 5ms 4ms 4ms 217.32.143.234
2 5ms 5ms 18ms 217.32.144.30
3 7ms 6ms 6ms 109.159.244.250
4 11ms 6ms 6ms 213.120.180.167
5 7ms 17ms 8ms 217.41.169.107
6 7ms 7ms 7ms 109.159.251.109
...
< Completed >
www.netflix.com[54.245.104.31] ,Maximum hops:30
1 5ms 5ms 5ms 217.32.143.234
2 5ms 5ms 5ms 217.32.144.30
3 8ms 9ms 8ms 213.120.181.26
4 8ms 14ms 8ms 213.120.180.167
5 9ms 10ms 11ms 217.41.169.107
6 7ms 8ms 7ms 109.159.251.85
...
< Completed >
www.facebook.com[31.13.80.65] ,Maximum hops:30
1 5ms 5ms 5ms 217.32.143.234
2 5ms 5ms 5ms 217.32.144.30
3 9ms 7ms 7ms 212.140.235.130
4 7ms 7ms 7ms 213.120.180.167
5 8ms 8ms 8ms 217.41.169.107
6 6ms 6ms 6ms 109.159.255.159
...
< Completed >
Tracertingwww.rt.com[62.213.85.4] ,Maximum hops:30
1 5ms 5ms 5ms 217.32.143.234
2 5ms 5ms 5ms 217.32.144.46
3 7ms 7ms 6ms 212.140.235.226
4 7ms 7ms 7ms 213.120.180.167
5 8ms 8ms 9ms 217.41.169.107
6 6ms 6ms 6ms 109.159.255.163
...
You get the idea. Before diverging still in BT's 21CN core, indeed still in Yorkshire at hop 6 - just entering BT's core network.