Quote:
Originally Posted by roughbeast
Definitely Coventry. It all gets routed through Birmingham after that.
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms REDDWARF [192.168.1.1]
2 7 ms 7 ms 7 ms 10.14.112.1
3 8 ms 7 ms 7 ms brhm-core-2b-ae3-938.network.virginmedia.net [21
3.106.230.157]
4 39 ms 8 ms 7 ms brhm-bb-1b-ae8-0.network.virginmedia.net [62.253
.174.77]
5 12 ms 132 ms 35 ms nrth-bb-1a-as4-0.network.virginmedia.net [62.253
.185.105]
6 18 ms 13 ms 13 ms nrth-bb-1b-ae0-0.network.virginmedia.net [62.253
.185.118]
7 16 ms 15 ms 15 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.
174.18]
8 15 ms 15 ms 15 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
9 * * * Request timed out.
10 15 ms 14 ms 16 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
11 17 ms 15 ms 15 ms 132.185.255.134
12 14 ms 15 ms 15 ms 212.58.241.131
Trace complete.
All tests done within a 10 minute slot. |
Looking at the two humps in the TBB graph and your traceroute - if the traceroute was taken while that was happening, and if there was congestionin the VM network (one of the possible causes), then all of the traces in that traceroute would have shown the same cdelay at and after a certain point in the list.
If the traceroute was not taken during the middle of that, there's nothing we can glean from it.
---------- Post added at 12:08 ---------- Previous post was at 11:57 ----------
Quote:
Originally Posted by qasdfdsaq
It isn't the core network. It's a few edge nodes. It's been showing up in Scotland since at least Feb 26th.
Both Roughbeast and Maverick's base latency makes it look like they're up north somewhere, in fact pretty much as far north as VM's network goes. Even though RB's profile says he's in Coventry.
And later you posted :
VM seem to have some very slow routes for some reason. Edinburgh to Manchester is a ~250 mile path, and takes only 5ms. Birmingham to London is about 100 miles but taking 8ms for you. Manchester to London, which is about twice as far, only takes 6-7ms for me.
(Incidentally VM also have a very slow route to Amsterdam)
Despite having over four times as far for my data to go, it only takes 15% longer (18ms) to reach London from Edinburgh than it does for you. My TBB monitor actually has the same minimum ping as yours, despite being 4 times further away as well, which is really odd.
.....?
|
So they're not in the furthest northern regions. I think Qasi is approaching this from the wrong angle. a 15% difference in transit times doesn't account for the minimum latency humps we're seeing.
It's one (or all) of three things:
1. LAN related issues
2. TBB glitching like it did earlier
3. Some issue in the Core as stuiff queues due to routing issues or whatever
Any traceroutes must be done during the peiod of the humps in order for there to be any deduction made, and, as Craigie has suggested, it should be back to the TBB site.
I wish this was Simples, because these are buggers to determine.