| [BC] Telus Routing.....145 ping to seattle? Crazy routing. HELP ME THE PHILLIPINES DON'T CARE!
C:\Users\Home>ping 63.208.142.131
Pinging 63.208.142.131 with 32 bytes of data:
Reply from 63.208.142.131: bytes=32 time=143ms TTL=57
Reply from 63.208.142.131: bytes=32 time=144ms TTL=57
Reply from 63.208.142.131: bytes=32 time=144ms TTL=57
Reply from 63.208.142.131: bytes=32 time=145ms TTL=57
Ping statistics for 63.208.142.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 143ms, Maximum = 145ms, Average = 144ms
C:\Users\Home>
C:\Users\Home>tracert 63.208.142.131
Tracing route to unknown.Level3.net [63.208.142.131]
over a maximum of 30 hops:
1 27 ms 26 ms 26 ms 142.179.120.254
2 25 ms 25 ms 25 ms 154.11.89.130
3 82 ms 81 ms 81 ms MTLXPQVVGR00.bb.telus.com [154.11.11.246]
4 92 ms 91 ms 90 ms ix-11-3-6-0.tcore1.MTT-Montreal.as6453.net [216.
6.115.57]
5 1000 ms 93 ms 93 ms 64.86.31.34
6 94 ms 99 ms 94 ms if-9-0-0-0.tcore2.NYY-NewYork.as6453.net [216.6.
99.9]
7 94 ms 93 ms 95 ms if-11-2.tcore1.NYY-NewYork.as6453.net [216.6.99.
2]
8 * * * Request timed out.
9 96 ms 96 ms 97 ms ae9.edge1.NewYork.Level3.net [4.68.62.185]
10 96 ms 96 ms 96 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
11 96 ms 95 ms 97 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
12 95 ms 95 ms 98 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
13 119 ms 121 ms 120 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
14 146 ms 158 ms 146 ms ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
15 147 ms 146 ms 145 ms ae-21-52.car1.Seattle1.Level3.net [4.69.147.163]
16 143 ms 143 ms 146 ms unknown.Level3.net [63.208.142.131]
Trace complete.
C:\Users\Home> |
|
| This has been discussed to death on the forums many times. Tech support will NOT be able to help you with routing. This has nothing to do with the Philippines either. |
|
 pfakBow before me for I am rootPremium
join:2002-12-29
Vancouver, BC
 ·TELUS
 ·Shaw
| reply to kennych
traceroute to 63.208.142.131 (63.208.142.131), 64 hops max, 52 byte packets
1 192.168.101.1 (192.168.101.1) 0.169 ms 0.112 ms 0.091 ms
2 204.14.120.65 (204.14.120.65) 0.431 ms 0.389 ms 0.426 ms
3 205.185.218.65 (205.185.218.65) 9.965 ms 11.359 ms 0.762 ms
4 te3-7.ccr01.sea02.atlas.cogentco.com (38.104.126.245) 0.491 ms 0.497 ms 0.473 ms
5 te7-8.ccr01.sea01.atlas.cogentco.com (154.54.82.37) 0.630 ms
te9-7.ccr01.sea01.atlas.cogentco.com (154.54.44.85) 0.590 ms
te9-8.ccr01.sea01.atlas.cogentco.com (154.54.44.89) 0.642 ms
6 te3-2.ccr01.smf01.atlas.cogentco.com (154.54.31.81) 20.003 ms
te7-4.ccr01.smf01.atlas.cogentco.com (154.54.40.105) 19.583 ms
te7-2.ccr01.smf01.atlas.cogentco.com (154.54.47.193) 19.553 ms
7 te0-0-0-1.ccr22.sfo01.atlas.cogentco.com (154.54.80.65) 19.719 ms
te0-0-0-1.mpd22.sfo01.atlas.cogentco.com (154.54.80.69) 19.700 ms
te0-0-0-1.ccr22.sfo01.atlas.cogentco.com (154.54.80.65) 19.587 ms
8 te4-4.ccr02.sjc01.atlas.cogentco.com (66.28.4.182) 19.625 ms
te1-7.ccr02.sjc01.atlas.cogentco.com (154.54.30.22) 19.610 ms
te1-2.ccr02.sjc01.atlas.cogentco.com (66.28.4.10) 19.548 ms
9 te4-2.ccr02.sjc03.atlas.cogentco.com (154.54.6.110) 19.555 ms 19.610 ms 19.610 ms
10 te-3-3.car3.SanJose1.Level3.net (4.68.110.137) 19.562 ms 19.577 ms 19.561 ms
11 vlan60.csw1.SanJose1.Level3.net (4.69.152.62) 20.035 ms 20.132 ms 20.095 ms
12 ae-62-62.ebr2.SanJose1.Level3.net (4.69.153.17) 20.046 ms 19.959 ms 20.040 ms
13 ae-7-7.ebr1.Seattle1.Level3.net (4.69.132.50) 46.238 ms 50.190 ms 37.667 ms
14 ae-11-51.car1.Seattle1.Level3.net (4.69.147.131) 37.577 ms 37.445 ms 37.870 ms
15 unknown.Level3.net (63.208.142.131) 37.797 ms 37.782 ms 38.027 ms
This destination IP address just has really bad routing, this is from my colocation in Seattle.
--
The more I C, the less I see. |
|
| Thats seattle.
Heres to RICHMOND from New Westminster
traceroute to (204.50.*.*), 30 hops max, 60 byte packets
1 . (192.168.12.254) 0.766 ms 0.598 ms 0.999 ms
2 10.149.96.1 (10.149.96.1) 10.279 ms 10.965 ms 10.963 ms
3 154.11.246.230 (154.11.246.230) 11.783 ms 13.809 ms 13.723 ms
4 173.182.214.131 (173.182.214.131) 11.909 ms 12.172 ms 12.082 ms
5 154.11.22.80 (154.11.22.80) 14.938 ms 14.991 ms 14.997 ms
6 154.11.10.230 (154.11.10.230) 15.007 ms 12.603 ms 204.225.243.22 (204.225.243.22) 12.948 ms
7 206.111.7.33.ptr.us.xo.net (206.111.7.33) 12.750 ms 38.811 ms 13.643 ms
8 vb2000d1.rar3.seattle-wa.us.xo.net (207.88.13.142) 16.885 ms 16.828 ms 16.803 ms
9 te-4-0-0.rar3.denver-co.us.xo.net (207.88.12.82) 70.938 ms 70.877 ms 70.790 ms
10 te-4-1-0.rar3.chicago-il.us.xo.net (207.88.12.21) 73.844 ms 73.764 ms 73.668 ms
11 * * *
12 216.156.72.34.ptr.us.xo.net (216.156.72.34) 76.186 ms 76.110 ms 75.974 ms
13 69.63.253.146 (69.63.253.146) 78.146 ms 79.786 ms 79.680 ms
14 so-0-0-0.gw02.mtnk.phub.net.cable.rogers.com (66.185.80.170) 74.661 ms 76.693 ms 76.707 ms
15 gw02.qcmtl.phub.net.cable.rogers.com (24.153.4.65) 75.698 ms 79.400 ms 79.462 ms
16 so-5-0-2.gw02.ym.phub.net.cable.rogers.com (24.153.4.82) 78.973 ms 78.976 ms 78.959 ms
17 rti2.bcvan.phub.net.cable.rogers.com (24.153.3.46) 75.895 ms 76.064 ms 76.022 ms
18 g6-1-S1.tls2.van1.rogerstelecom.net (204.50.128.122) 77.264 ms 77.216 ms 77.876 ms
19 Z-a3-0-0-439-S1.tls2.van1.rogerstelecom.net (204.50.21.174) 77.884 ms 77.811 ms 77.716 ms
GL getting Help OP |
|
pfakBow before me for I am rootPremium
join:2002-12-29
Vancouver, BC | That's Rogers for you, same situation for Bell. But there's the same problems with Shaw to Rogers and Shaw to Bell.
--
The more I C, the less I see. |
|
| reply to kennych
Yeah, basically "deal with it."
Telus routing is terrible, but it's a small price to pay for the improved service I get compared to Shaw.
For the MMO I play (APB Reloaded) the latency to the East coast servers is lower than West because Telus sends it all over to Toronto before down to either Washington DC or Los Angeles. |
|
|
|
 XT0RTS3x, Drugs, War
join:2001-07-28
Edmonton, AB | reply to kennych
Notice that part in your tracert that says Level3? There's your problem right there. |
|
