[Sephiroth]

Originally Posted by qasdfdsaq

No, but their latency looks like they should be, if it takes longer for data to go from London to Birmingham than London to Edinburgh, something is wrong with the route it's taking. His base ping should be around the 10ms mark, not the 16-18 it's showing on the chart.

SEPH: I don't know how you get to the "base poing" being 10 ms. What does "base ping" mean?

I traced to Namesco's BBMAX speedtest site:

Tracing route to speedtest.bbmax.co.uk [85.233.160.167] over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 192.168.1.1
2 18 ms 33 ms 24 ms 10.159.48.1
3 9 ms 35 ms 39 ms winn-core-1a-ae1-955.network.virginmedia.net [62.253.121.77]
4 11 ms 27 ms 24 ms winn-bb-1a-so-130-0.network.virginmedia.net [62.253.184.113]
5 18 ms 20 ms 65 ms popl-bb-1b-as5-0.network.virginmedia.net [212.43.162.194]
6 34 ms 10 ms 11 ms tele-ic-5-ae0-0.network.virginmedia.net [213.105.159.117]
7 10 ms 18 ms 27 ms linx-gw2.plus.net [195.66.236.164]
8 43 ms 20 ms 19 ms po4.ptn-gw01.plus.net [212.159.1.138]
9 33 ms 39 ms 15 ms ptw3-gi2-3.namesco.net [212.159.1.66]
10 23 ms 16 ms 16 ms gonzales.namesco.net [85.233.160.167]

No strange routing but the lowest ping time to the destination was 16 ms. The North of the UK stuff was a comlete red herring.


The 15% was an illustration of my speed vs. theirs, it has nothing to do with the humps RB is seeing.
SEPH: Aren't we trying to explain the humps? They were even larger in earlier posts. The context in which I mentioned the Core was the humps and your response was also in that context.


Their latency (or rather the latency during the traceroute) shows either the route is very slow or alternatively taking a bad route - e.g. going Birmingham => Manchester => London. Route flapping between direct and indirect routes like that could explain the humps, but so could congestion. Or even the latter causing the former.
SEPH: So we are considering the humps. Route flapping is a plausible explanation because it builds queues in various places.


I think the problem is, well, there's two problems which are impossible to isolate from each other.

Since it affects nodes within VM's carrier network then it can't be purely a LAN issue

If that were the case you'd expect it to affect many/every route/destination along certain paths. It doesn't

Most likely explanation.

Indeed - pingbox1.thinkbroadband.com

SEPH: In the generic sense, it would have to be one of the three I listed. I too didn't think LAN in the specific case. So now you think it's TBB? You didn't think so earlier. Or have I misunderstood you?