Quote:
Originally Posted by Sephiroth
So they're not in the furthest northern regions.
|
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.
Quote:
|
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.
|
The 15% was an illustration of my speed vs. theirs, it has nothing to do with the humps RB is seeing.
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.
I think the problem is, well, there's two problems which are impossible to isolate from each other.
Quote:
It's one (or all) of three things:
1. LAN related issues
|
Since it affects nodes within VM's carrier network then it can't be purely a LAN issue
Quote:
|
2. TBB glitching like it did earlier
|
If that were the case you'd expect it to affect many/every route/destination along certain paths. It doesn't
Quote:
|
3. Some issue in the Core as stuiff queues due to routing issues or whatever
|
Most likely explanation.
Quote:
|
and, as Craigie has suggested, it should be back to the TBB site.
|
Indeed - pingbox1.thinkbroadband.com