Quote:
Originally Posted by pip08456
Goes via NL for me.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>tracert 199.27.135.74
Tracing route to cf-199-27-135-74.cloudflare.com [199.27.135.74]
over a maximum of 30 hops:
1 59 ms 57 ms 80 ms cpc8-bary4-2-0-gw.5-1.cable.virginmedia.com [82.
8.40.1]
2 54 ms 11 ms 57 ms cdif-core-1a-ge-300-935.network.virginmedia.net
[62.254.252.29]
3 108 ms 40 ms 213 ms brhm-bb-1a-as0-0.network.virginmedia.net [212.43
.163.109]
4 12 ms 57 ms 57 ms manc-bb-1b-ae5-0.network.virginmedia.net [213.10
5.174.186]
5 17 ms 19 ms 61 ms popl-bb-1a-as4-0.network.virginmedia.net [212.43
.162.85]
6 62 ms 21 ms 17 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.10
5.159.2]
7 72 ms 69 ms 69 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
8 72 ms 69 ms 69 ms ams-ix.ae1.cr1.ams2.nl.nlayer.net [195.69.145.21
9]
9 69 ms 69 ms 69 ms ae3-60g.cr1.ams2.nl.nlayer.net [69.22.139.238]
10 69 ms 69 ms 69 ms xe-1-3-0-111.cr1.ams2.nl.nlayer.net [69.22.139.2
]
11 27 ms 73 ms 73 ms 51.vlan.ar1.ams3.nl.scnet.net [205.234.220.194]
12 27 ms 45 ms 73 ms ge0-4.aggrB3.ams3.nl.scnet.net [205.234.220.231]
13 30 ms 73 ms 27 ms cf-199-27-131-10.cloudflare.com [199.27.131.10]
14 73 ms 27 ms 73 ms cf-199-27-135-74.cloudflare.com [199.27.135.74]
Trace complete.
C:\Documents and Settings\Administrator>
|
I had to check yours twice, very dodgy latency VM side made me think was .us ;P
but yeah your result another example of how routing is luck of the draw on an isp as different ip ranges get routed differently.
on the .us fubared routes VM appear to have a direct link with nlayer who do have a EU presence so it seems quite bizarre, or maybe the arrangement is only a .us handover. For a large isp VM seem to have poor peering.
Mine below.
1 <1 ms <1 ms <1 ms home.gateway2 [192.168.1.1]
2 7 ms 8 ms 11 ms cpc14-leic14-2-0-gw.8-1.cable.virginmedia.com [8
2.30.112.1]
3 9 ms 5 ms 7 ms leic-core-1a-ae3-3495.network.virginmedia.net [8
2.3.33.101]
4 14 ms 8 ms 12 ms leed-bb-1a-as8-0.network.virginmedia.net [213.10
5.172.17]
5 15 ms 17 ms 18 ms popl-bb-1b-as1-0.network.virginmedia.net [62.253
.185.238]
6 16 ms 14 ms 17 ms popl-tmr-2-ae5-0.network.virginmedia.net [213.10
5.159.6]
7 18 ms 17 ms 16 ms tele-ic-2-as0-0.network.virginmedia.net [62.253.
184.6]
8 88 ms 87 ms 112 ms eqix.xe-3-3-0.cr2.iad1.us.nlayer.net [206.223.11
5.61]
9 85 ms 97 ms 88 ms ae2-30g.ar2.iad1.us.nlayer.net [69.31.31.186]
10 87 ms 90 ms 90 ms as13335.ge-0-0-33.ar2.iad1.us.nlayer.net [69.31.
30.26]
11 86 ms 88 ms 86 ms cf-199-27-135-74.cloudflare.com [199.27.135.74]
---------- Post added at 22:02 ---------- Previous post was at 21:59 ----------
I suggest getting back to cloudflare and ask them what this EU route is, then you can go back to VM and say I know this route exists why arent you using it. Ask VM's NOC or tier2 forum support I wouldnt bother on the phones.
cloudflare probably could fix it themselves but it sounds like they not motivated enough.
---------- Post added at 22:06 ---------- Previous post was at 22:02 ----------
I tried tracerouting to 2 ip's found on pip's trace. It seems that direct ams-ix link is simply disabled for a chunk of VM's network this did go without .us but had to go over above.net 3rd party transit. So this shows VM have a alternate EU route available via abovenet.
Tracing route to ams-ix-2.microsoft.com [195.69.145.21]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway2 [192.168.1.1]
2 6 ms 7 ms 6 ms cpc14-leic14-2-0-gw.8-1.cable.virginmedia.com [8
2.30.112.1]
3 9 ms 6 ms 7 ms leic-core-1a-ae3-2232.network.virginmedia.net [8
2.3.33.49]
4 15 ms 11 ms 11 ms leed-bb-1a-as8-0.network.virginmedia.net [213.10
5.172.17]
5 14 ms 15 ms 15 ms 213.152.245.53
6 15 ms 47 ms 15 ms ge-4-2-0.mpr1.lhr3.uk.above.net [64.125.27.157]
7 23 ms 25 ms 22 ms so-0-1-0.mpr1.ams1.nl.above.net [64.125.27.221]
8 21 ms 22 ms 23 ms xe-0-0-0.er1.ams1.nl.above.net [64.125.26.81]
9 25 ms 32 ms 23 ms ams-ix-2.microsoft.com [195.69.145.21]
and
Tracing route to amst-ic-1-as0-0.network.virginmedia.net [213.105.175.6]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway2 [192.168.1.1]
2 26 ms 7 ms 5 ms cpc14-leic14-2-0-gw.8-1.cable.virginmedia.com [8
2.30.112.1]
3 21 ms 18 ms 14 ms leic-core-1a-ae3-2232.network.virginmedia.net [8
2.3.33.49]
4 43 ms 12 ms 10 ms leed-bb-1a-as8-0.network.virginmedia.net [213.10
5.172.17]
5 15 ms 14 ms 17 ms popl-bb-1b-as1-0.network.virginmedia.net [62.253
.185.238]
6 15 ms 15 ms 10 ms popl-bb-1a-ae0-0.network.virginmedia.net [213.10
5.174.229]
7 16 ms 13 ms 12 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.10
5.159.2]
8 23 ms 21 ms 20 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
personally I think its all down to saturation of links or possibly down to trying to have active redundancy, I still get routed via leeds to everywhere which suggests the internal VM network has a saturation point forcing that reroute, and after that then there is all this alternate routing going on which suggests VM do not have the capacity to route their entire customer base on optimal routing.