[Chrysalis]

ok regarding different external routes been used for different ntl area's this caught my attention. A ntl user was complaing of problem with his WoW connection and posted the following traceroute.

1 <1 ms <1 ms <1 ms air.setup [192.168.11.1]
2 11 ms 19 ms 7 ms 10.152.71.254
3 14 ms 9 ms 7 ms rdng-t2cam1-b-ge94.inet.ntl.com [62.253.122.137]
4 94 ms 62 ms 62 ms winn-t2core-b-ge-wan62.inet.ntl.com [62.253.121.149]
5 12 ms 9 ms 7 ms win-bb-b-so-300-0.inet.ntl.com [213.105.174.101]
6 1527 ms 1513 ms 1495 ms po4-0.brsbb1.bristol.opentransit.net [193.251.254.145]
7 1521 ms 1548 ms 1543 ms po8-0.loncr3.london.opentransit.net [193.251.243.37]
8 1586 ms 1575 ms 1553 ms po3-0.nykcr3.newyork.opentransit.net [193.251.243.21]
9 1551 ms 1552 ms 1592 ms ft-gw.n54ny.ip.att.net [192.205.32.137]
10 1667 ms 1634 ms 1614 ms tbr1-p032501.n54ny.ip.att.net [12.122.80.22]
11 1604 ms 1601 ms 1598 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
12 1629 ms 1671 ms 1626 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
13 1646 ms 1672 ms 1698 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
14 1718 ms 1736 ms 1701 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255.254]
15 1705 ms 1740 ms 1740 ms mdf1-bi8k-1-eth-2-4.lax1.attens.net [12.129.192.62]
16 * * * Request timed out.

If I am right he is in reading near london.

I decided to trace the same ip and got the following.

1 27 ms 8 ms 12 ms UBR [10.8.143.254]
2 11 ms 11 ms 13 ms leic-t2cam1-a-ge914.inet.ntl.com [82.3.35.149]
3 9 ms 13 ms 75 ms leic-t2core-a-ge-220-0.inet.ntl.com [82.3.33.10]
4 12 ms 19 ms 24 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110]
5 23 ms 28 ms 14 ms lee-bb-b-ae0-0.inet.ntl.com [62.253.187.186]
6 53 ms 18 ms 13 ms man-bb-a-so-700-0.inet.ntl.com [62.253.185.193]
7 25 ms 24 ms 26 ms 212.187.137.1
8 28 ms 57 ms 37 ms so-6-1-0.mp2.manchesteruk1.level3.net [4.68.113.
118]
9 91 ms 109 ms 90 ms ae-0-0.bbr2.newyork1.level3.net [64.159.1.42]
10 91 ms 92 ms 107 ms ae-23-54.car3.newyork.level3.net [4.68.97.114]
11 103 ms 136 ms 93 ms att-level3-oc48.newyork1.level3.net [4.68.127.6]
12 184 ms 199 ms 183 ms tbr1-p032501.n54ny.ip.att.net [12.122.80.22]
13 167 ms 160 ms 162 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2]
14 162 ms 168 ms 163 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
15 158 ms 195 ms 160 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
16 191 ms 202 ms 167 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
17 179 ms 161 ms 162 ms mdf1-bi8k-1-eth-2-4.lax1.attens.net [12.129.192.
62]
18 ^C

Ok so different route, so I thought maybe they rerouted it after he managed to get thru to tier2 support so for good measure I traced a opentransit hop to see what route I got to it and to see if problematic.


1 32 ms 10 ms 34 ms UBR [10.8.143.254]
2 9 ms 9 ms 7 ms leic-t2cam1-a-ge914.inet.ntl.com [82.3.35.149]
3 9 ms 10 ms 10 ms leic-t2core-a-ge-220-0.inet.ntl.com [82.3.33.10]
4 25 ms 17 ms 12 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110]
5 32 ms 14 ms 37 ms nth-bb-b-so-000-0.inet.ntl.com [62.253.185.101]
6 18 ms 33 ms 17 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
7 21 ms 32 ms 22 ms so-2-2-0-0.loncr2.london.opentransit.net [193.251.254.141]
8 71 ms 56 ms 23 ms po2-0.loncr3.london.opentransit.net [193.251.242.21]
9 97 ms 109 ms 93 ms po3-0.nykcr3.newyork.opentransit.net [193.251.243.21]

Appears no problem, can someone in the south of england trace us.logon.worldofwarcraft.com please that was the target he traced so can see if the routing is indeed different, this could explain the hige differences in performances different areas appear to have.

---------- Post added at 21:04 ---------- Previous post was at 21:01 ----------

ip 12.129.232.116 as it is a pool of ip's I want to make sure same destination.