Not directly it doesn't But it does highlight a similar issue with the way That the IP the game i play uses
216.98.48.56 is getting routed indirectly (London to Paris back to London again) before transiting to NewYork that is for some reason apparent if connected to some of your Gateways, Fortunately not all of them,
Which if i currently wasn't using a gateway which routes London directly to NewYork ,Which is surely the correct way in which to route traffic? I would have that issue in the other post on top of this issue of AS6453.net routing traffic from NewYork to
Chicago!!! Before routing to Montreal Are AS6453.net for real?
Hence my enquiry regarding the use of a different peering company, who preferably routes traffic directly
For other Tracert results it does seem that AS6453.net have changed the routing path from NewYork to Montreal for some reason, But other tracert results are giving a slightly better /lower ping Maybe level3 need a prodding re this
From Level 3 looking glass
Traceroute results from London, England (2)
to 216.98.48.56(lb-lsg-prod.ubisoft.com)
1 ae-15-15.edge3.London2.Level3.net (4.69.200.85) 48 msec 0 msec 60 msec
2 ae-3-3.ebr1.Paris1.Level3.net (4.69.141.86) 92 msec 28 msec 28 msec
3 ae-71-71.csw2.Paris1.Level3.net (4.69.161.82) 16 msec
ae-81-81.csw3.Paris1.Level3.net (4.69.161.86) 52 msec
ae-91-91.csw4.Paris1.Level3.net (4.69.161.90) 108 msec
4 4.69.168.8 112 msec
4.69.168.136 44 msec
4.69.168.200 52 msec
5 ix-20-0.tcore1.PVU-Paris.as6453.net (80.231.153.65) [AS6453 {GLOBEINTERNET}] 204 msec 204 msec 204 msec
6 if-2-2.tcore1.PYE-Paris.as6453.net (80.231.154.18) [AS6453 {GLOBEINTERNET}] 216 msec 200 msec
if-12-2.tcore1.PYE-Paris.as6453.net (80.231.154.69) [AS6453 {GLOBEINTERNET}] 204 msec
7 if-3-6.tcore1.L78-London.as6453.net (80.231.130.85) [AS6453 {GLOBEINTERNET}] 124 msec 212 msec
if-5-2.tcore1.L78-London.as6453.net (80.231.130.1) [AS6453 {GLOBEINTERNET}] 76 msec
8 if-1-2.tcore2.L78-London.as6453.net (80.231.130.122) [AS6453 {GLOBEINTERNET}] 204 msec
if-2-2.tcore2.L78-London.as6453.net (80.231.131.1) [AS6453 {GLOBEINTERNET}] 216 msec 212 msec
9 if-20-2.tcore2.NYY-NewYork.as6453.net (216.6.99.13) [AS6453 {GLOBEINTERNET}] 204 msec * 136 msec
10 if-12-6.tcore1.CT8-Chicago.as6453.net (216.6.99.46) [AS6453 {GLOBEINTERNET}] 220 msec * 108 msec
11 if-22-2.tcore2.CT8-Chicago.as6453.net (64.86.79.1) [AS6453 {GLOBEINTERNET}] 124 msec 112 msec *
12 if-3-2.tcore1.W6C-Montreal.as6453.net (66.198.96.45) [AS6453 {GLOBEINTERNET}] 132 msec 116 msec 120 msec
13 * *
66.198.96.18 [AS6453 {GLOBEINTERNET}] !filtered
From AS6453.net looking glass
Router: gin-ldn-core4
Site: UK, London, LDN
Command: traceroute ip 216.98.48.56
Tracing the route to lb-lsg-prod.ubisoft.com (216.98.48.56)
1 if-4-3-2-0.tcore2.LDN-London.as6453.net (80.231.20.37) [MPLS: Label 302065 Exp 0] 96 msec
if-0-1-3-0.tcore2.LDN-London.as6453.net (80.231.62.25) [MPLS: Label 302065 Exp 0] 96 msec
if-3-1-2-12.tcore2.LDN-London.as6453.net (80.231.62.29) [MPLS: Label 302065 Exp 0] 100 msec
2 if-15-2.tcore2.L78-London.as6453.net (80.231.131.117) [MPLS: Label 725890 Exp 0] 96 msec 96 msec 96 msec
3 if-20-2.tcore2.NYY-NewYork.as6453.net (216.6.99.13) [MPLS: Label 349761 Exp 0] 96 msec 108 msec 96 msec
4 if-12-6.tcore1.CT8-Chicago.as6453.net (216.6.99.46) [MPLS: Label 384049 Exp 0] 100 msec 100 msec 96 msec
5 if-22-2.tcore2.CT8-Chicago.as6453.net (64.86.79.1) [MPLS: Label 391169 Exp 0] 100 msec 96 msec 96 msec
6 if-3-2.tcore1.W6C-Montreal.as6453.net (66.198.96.45) 112 msec 96 msec 100 msec
And some direct routing from London to NewYork
Traceroute results from London, England
to 216.98.48.56(lb-lsg-prod.ubisoft.com)
1 ae-52-52.csw2.London1.Level3.net (4.69.139.120) 0 msec
ae-51-51.csw1.London1.Level3.net (4.69.139.88) 0 msec
ae-52-52.csw2.London1.Level3.net (4.69.139.120) 8 msec
2 ae-115-3501.edge3.London1.Level3.net (4.69.166.130) 0 msec
ae-225-3601.edge3.London1.Level3.net (4.69.166.146) 228 msec
ae-116-3502.edge3.London1.Level3.net (4.69.166.134) 0 msec
3 ix-20-0.tcore1.LDN-London.as6453.net (195.219.83.101) [AS6453 {GLOBEINTERNET}] 0 msec 0 msec 0 msec
4 *
if-17-2.tcore1.L78-London.as6453.net (80.231.130.129) [AS6453 {GLOBEINTERNET}] 408 msec 212 msec
5 if-1-2.tcore2.L78-London.as6453.net (80.231.130.122) [AS6453 {GLOBEINTERNET}] 160 msec
if-2-2.tcore2.L78-London.as6453.net (80.231.131.1) [AS6453 {GLOBEINTERNET}] 204 msec 228 msec
6 if-20-2.tcore2.NYY-NewYork.as6453.net (216.6.99.13) [AS6453 {GLOBEINTERNET}] 204 msec * *
7 if-12-6.tcore1.CT8-Chicago.as6453.net (216.6.99.46) [AS6453 {GLOBEINTERNET}] 112 msec 92 msec 96 msec
8 if-22-2.tcore2.CT8-Chicago.as6453.net (64.86.79.1) [AS6453 {GLOBEINTERNET}] 92 msec 96 msec 96 msec
9 if-3-2.tcore1.W6C-Montreal.as6453.net (66.198.96.45) [AS6453 {GLOBEINTERNET}] 92 msec 132 msec 92 msec
10 * * *
11 * * *
12 * * *
13 * * *
14 66.198.96.18 [AS6453 {GLOBEINTERNET}] !filtered * *
http://lookingglass.level3.net/index.html http://lg.as6453.net/lg/ Level3 aren't exactly brilliant on peering either certainly to montreal and other transatlantic routes, and all the rtt results are higher than they where just over a month ago , for instance Newyork was nearly always 80ms or less and my ping times with the different ISP's for years have never been over 100ms the average for me was 95ms max 98ms and as i said until they started routing via Chicago on plusnet it was 89-90ms more or less all the time, only times it increased apart from the paris level3 routing as per other post, was what appeared to be peak time congestion effects which could occur at different times of the day or night , So could be level3 or AS6453.net are/have been running some links too hot at times
