connormc

Poor Shaw Peering/Routing.

Discussion created by connormc on Nov 20, 2013
Latest reply on Nov 21, 2013 by shaw-matt

ever since i signed up with shaw my ping to eastcoast have been extremely inconcistent, because shaw is retarted enough to rout my east coast traffic through edmonton most of the time adding 40ms to my ping because the shaw is to stupid to peer with companies like level 3 and hurricane electric, there choosing to move traffic through there own lines, even if it adds mass amount of latency, if my traffic could stop going through edmonton all together i will be happy, if not i will be leaving shaw in may and switching to TSI as they do peer with much better companies and switching to them would remedy the problem shaw is creating by trying to save money.. every single ip i can throw at a TSI west user gets better response times, EVERY SINGLE IP, not just some!

 

here are traceroutes from me to texas, most of the time it goes through edmonton, but im showing other paths aswell so show how much faster they would be. i have also been told my shaw employee's this happens because shaws old HQ is in edmonton, this is not acceptable. screw edmonton. my traffic should NEVER go there. and it WILL NOT go there pointlessly through any other canadian isp's so this is a SHAW PROBLEM

here is through Edmonton to Houston.
C:\Users\Connor>tracert 204.2.20.30

 

Tracing route to phonoscope-204-2-20-030.phonoscope.com [204.2.20.30]
over a maximum of 30 hops:

 

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 20 ms 15 ms 19 ms 64.59.156.243
4 18 ms 15 ms 15 ms rc2bb-tge0-4-0-16.vc.shawcable.net [66.163.69.21
8]
5 33 ms 31 ms 31 ms 66.163.75.202
6 30 ms 32 ms 31 ms rc1we-hge0-4-0-0.ed.shawcable.net [66.163.70.66]

 

7 63 ms 51 ms 43 ms rc3sc-tge0-0-0-9.wp.shawcable.net [66.163.78.70]

 

8 73 ms 78 ms 75 ms rc3ec-tge0-11-0-13.il.shawcable.net [66.163.78.5
0]
9 72 ms 74 ms 75 ms xe-0-6-0-2.r05.chcgil09.us.bb.gin.ntt.net [128.2
42.186.169]
10 72 ms 73 ms 76 ms ae-6.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.2
6]
11 96 ms 98 ms 93 ms ae-3.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.2
00]
12 98 ms 108 ms 98 ms ae-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.5
8]
13 104 ms 99 ms 113 ms ae-3.r04.hstntx01.us.bb.gin.ntt.net [129.250.5.2
26]
14 116 ms 108 ms 100 ms bbr1.phonoscope.com [128.241.5.5]
15 125 ms 103 ms 116 ms phonoscope-204-2-20-030.phonoscope.com [204.2.20
.30]
Trace complete.

 

next is through Calgary to Dallas

 

tracert 108.61.239.220

 

Tracing route to 108.61.239.220.choopa.net [108.61.239.220]
over a maximum of 30 hops:

 

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 18 ms 15 ms 15 ms 64.59.156.243
4 18 ms 15 ms 14 ms rc2bb-tge0-13-0-4.vc.shawcable.net [66.163.69.81
]
5 17 ms 23 ms 23 ms rc2wh-tge0-6-0-3.vc.shawcable.net [66.163.69.174
]
6 25 ms 27 ms 29 ms rc2so-tge0-5-0-0.cg.shawcable.net [66.163.77.22]

 

7 41 ms 43 ms 44 ms 66.163.75.122
8 56 ms 57 ms 57 ms rc3ec-tge0-11-0-15.il.shawcable.net [66.163.77.2
02]
9 60 ms 86 ms 59 ms equinix.xe-1-3-0.cr2.ord1.us.nlayer.net [206.223
.119.61]
10 57 ms 61 ms 62 ms ae3-60g.cr1.ord1.us.nlayer.net [69.31.111.153]
11 83 ms 80 ms 84 ms xe-3-3-0.cr1.dfw1.us.nlayer.net [69.22.142.5]
12 84 ms 85 ms 81 ms as20473.xe-5-1-2.cr1.dfw1.us.nlayer.net [69.31.6
3.238]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 83 ms 83 ms 83 ms 108.61.239.220.choopa.net [108.61.239.220]

 

last but not least San Jose to Houston.

 

tracert 209.62.1.2

 

Tracing route to ev1s-209-62-1-2.theplanet.com [209.62.1.2]
over a maximum of 30 hops:

 

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 18 ms 20 ms 15 ms 64.59.156.243
4 24 ms 14 ms 15 ms rc2bb-tge0-13-0-1.vc.shawcable.net [66.163.69.49
]
5 46 ms 51 ms 50 ms rc3sj-tge0-8-1-0.cl.shawcable.net [66.163.78.126
]
6 43 ms 73 ms 38 ms te1-7.bbr01.eq01.sjc01.networklayer.com [206.223
.116.176]
7 43 ms 35 ms 37 ms ae7.bbr02.eq01.sjc02.networklayer.com [173.192.1
8.165]
8 47 ms 43 ms 49 ms ae0.bbr02.cs01.lax01.networklayer.com [173.192.1
8.151]
9 53 ms 53 ms 55 ms ae7.bbr01.cs01.lax01.networklayer.com [173.192.1
8.166]
10 76 ms 79 ms 81 ms ae19.bbr01.eq01.dal03.networklayer.com [173.192.
18.140]
11 85 ms 83 ms 85 ms ae0.bbr01.sr02.hou02.networklayer.com [173.192.1
8.219]
12 86 ms 92 ms 89 ms po31.dsr02.hstntx2.networklayer.com [173.192.18.
235]
13 80 ms 83 ms 80 ms te4-1.car14.hstntx2.networklayer.com [74.55.252.
222]
14 84 ms 79 ms 79 ms ev1s-209-62-1-2.theplanet.com [209.62.1.2]

 

Trace complete.


 

Outcomes