[Hands0n]

How ridiculous is this then?

We all know that mobile operator "broadband" networks are anything but, often. And it is no wonder when you run a simple Traceroute and find that [at Vodafone] your data takes nine, possibly ten, hops around the internal
Vodafone network before leaving to join the peering network run by Global Crossing.

From there it is a mere four hops, one more at Global and three at the BBC to finally hit the target host.

Any network engineer worth their salt will tell you that each hop adds to latency and thus the design goal is to reduce the number of these to the barest minimum.

Back to school for you Vodafone!



C:\Documents and Settings>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 586 ms 309 ms 309 ms 10.252.224.61
2 329 ms 339 ms 339 ms 10.252.224.58
3 275 ms 309 ms 319 ms host206.msm.che.vodafone [10.206.64.4]
4 268 ms 309 ms 359 ms host206.msm.che.vodafone [10.206.65.1]
5 275 ms 319 ms 309 ms host206.msm.che.vodafone [10.206.65.135]
6 262 ms 319 ms 309 ms host206.msm.che.vodafone [10.206.66.68]
7 277 ms 319 ms 339 ms host206.msm.che.vodafone [10.206.66.193]
8 274 ms 319 ms 319 ms host206.msm.che.vodafone [10.206.66.212]
9 291 ms 409 ms 309 ms host206.msm.che.vodafone [10.206.70.157]
10 * * * Request timed out.
11 278 ms 369 ms 389 ms TenGigabitEthernet7-1.ar6.LON3.gblx.net [64.214.
144.121]
12 * * * Request timed out.
13 288 ms 349 ms 359 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.10
3]
14 309 ms 439 ms 329 ms 212.58.238.153
15 307 ms 349 ms 379 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

[Ben]

LoL yes, got to love bouncing around Vodafone's maze of a network :D How they manage all those hops and still low latency is beyond me... still, if every one of those was a meddling cache or irritating content control server it wouldn't surprise me. Vodafone, like some of the other networks, are a b*tch for blocking anything they don't commercially agree with under the guise of 'protection' :)

Open it up!