AnsweredAssumed Answered

Bad Shaw routing?

Question asked by emkoemko on Feb 11, 2017
Latest reply on May 9, 2017 by shaw-tony

According to the service department at Colocrossing this is on Shaws end. I need someone to confirm or deny this so i can have the issue addressed by Colocrossing and hopefully, if not Colocrossing you guys can help.

Here is my trace route to colocrossing Dallas server, i get around 15-20 hops with 90-120ms but when i do a traceroute from Dallas colocrossing to my home IP im getting a consistent 9 hops with 50-60 ms.

 

3 examples:

Tracing route to lg.dal.colocrossing.com [96.8.115.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.1.1]
2 13 ms 9 ms 10 ms 68.145.32.1
3 13 ms 15 ms 10 ms rc3so-be103-1.cg.shawcable.net [64.59.133.113]
4 39 ms 44 ms 41 ms rc4ec-be13.il.shawcable.net [66.163.65.18]
5 39 ms 41 ms 39 ms equinix-chi.suddenlink.NET [206.223.119.72]
6 86 ms 89 ms 97 ms 173-219-238-49.suddenlink.net [173.219.238.49]
7 353 ms 322 ms 421 ms 173-219-236-26.suddenlink.net [173.219.236.26]
8 87 ms 90 ms 85 ms 173-219-230-154.suddenlink.net [173.219.230.154]
9 90 ms * 86 ms 173-219-246-93.suddenlink.net [173.219.246.93]
10 103 ms * 97 ms xe-0-4-0-12.r01.dllstx04.us.bb.gin.ntt.net [129.250.202.253]
11 104 ms 98 ms 96 ms ae-0.xo-communications.dllstx04.us.bb.gin.ntt.net [129.250.9.158]
12 85 ms 86 ms 86 ms 207.88.14.188.ptr.us.xo.net [207.88.14.188]
13 85 ms 85 ms 86 ms 216.156.16.157.ptr.us.xo.net [216.156.16.157]
14 88 ms 86 ms 87 ms 64.0.175.122.ptr.us.xo.net [64.0.175.122]
15 * * * Request timed out.
16 106 ms * 200 ms lg.dal.colocrossing.com [96.8.115.5]
17 87 ms 86 ms 90 ms lg.dal.colocrossing.com [96.8.115.5]
18 86 ms 86 ms 94 ms lg.dal.colocrossing.com [96.8.115.5]

example:2

1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.1.1]
2 58 ms 20 ms 11 ms 68.145.32.1
3 19 ms 19 ms 8 ms rc3so-be103-1.cg.shawcable.net [64.59.133.113]
4 34 ms 26 ms 31 ms rc3sc-be110-1.wp.shawcable.net [66.163.76.62]
5 80 ms 70 ms 71 ms rc2as-be5.vx.shawcable.net [66.163.77.50]
6 69 ms 61 ms 62 ms eqx.20ge.iad.bboi.net [206.126.236.47]
7 96 ms 87 ms 90 ms mia-ten3-2-ash-ten7-5.bboi.net [66.216.1.121]
8 97 ms 96 ms 97 ms 66.216.0.186
9 93 ms 94 ms 89 ms 66.103.15.101
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 98 ms 99 ms 101 ms 173.199.235.70
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.

 

 

 

example 3 :
1 2 ms <1 ms 1 ms pfSense.localdomain [192.168.1.1]
2 10 ms 9 ms 9 ms 68.145.32.1
3 10 ms 12 ms 19 ms rc3so-be103-1.cg.shawcable.net [64.59.133.113]
4 23 ms 23 ms 26 ms rc3sc-be110-1.wp.shawcable.net [66.163.76.62]
5 73 ms 71 ms 70 ms rc2as-be5.vx.shawcable.net [66.163.77.50]
6 63 ms 62 ms 61 ms eqx.20ge.iad.bboi.net [206.126.236.47]
7 87 ms 87 ms 87 ms mia-ten3-2-ash-ten7-5.bboi.net [66.216.1.121]
8 97 ms 97 ms 105 ms 66.216.0.186
9 90 ms 90 ms 93 ms 66.103.15.101
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 138 ms * 103 ms 173.199.235.70
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 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.

 

 


From Dallas to Calgary

 

EXAMPLE 1

traceroute to 68.145.135.96 (68.145.135.96), 30 hops max, 60 byte packets
 1  10.2.4.85 (10.2.4.85)  0.024 ms  0.008 ms  0.007 ms
 2  10.2.3.237 (10.2.3.237)  1.092 ms  1.817 ms  2.558 ms
 3  10.2.5.17 (10.2.5.17)  0.401 ms  0.390 ms 10.2.5.21 (10.2.5.21)  0.368 ms
 4  dls-b21-link.telia.net (62.115.144.112)  0.470 ms dls-b21-link.telia.net (62.115.144.110)  0.419 ms dls-b21-link.telia.net (62.115.144.112)  0.437 ms
 5  kanc-b1-link.telia.net (62.115.125.40)  10.828 ms kanc-b1-link.telia.net (62.115.123.204)  10.831 ms kanc-b1-link.telia.net (213.155.130.179)  10.760 ms
 6  chi-b21-link.telia.net (62.115.123.199)  23.535 ms  23.481 ms chi-b21-link.telia.net (62.115.116.151)  23.543 ms
 7  shawbusiness-ic-300304-chi-b21.c.telia.net (62.115.12.86)  22.720 ms shawbusiness-ic-157037-chi-b21.c.telia.net (62.115.9.214)  22.620 ms shawbusiness-ic-157038-chi-b21.c.telia.net (62.115.9.78)  48.417 ms
 8  66.163.65.17 (66.163.65.17)  54.091 ms  54.073 ms  54.065 ms
 9  dx5ru-la0-s1.cg.int.shawcable.net (64.59.133.114)  58.000 ms  57.903 ms  58.179 ms

 

Example 2

 

traceroute to 68.145.135.96 (68.145.135.96), 30 hops max, 60 byte packets
 1  10.2.4.85 (10.2.4.85)  0.025 ms  0.009 ms  0.008 ms
 2  10.2.3.237 (10.2.3.237)  1.084 ms  1.828 ms  2.526 ms
 3  10.2.5.17 (10.2.5.17)  0.322 ms 10.2.5.21 (10.2.5.21)  38.737 ms 10.2.5.17 (10.2.5.17)  0.230 ms
 4  dls-b21-link.telia.net (62.115.144.112)  0.443 ms dls-b21-link.telia.net (62.115.144.110)  0.546 ms  0.522 ms
 5  kanc-b1-link.telia.net (62.115.135.38)  10.893 ms kanc-b1-link.telia.net (62.115.125.46)  10.828 ms kanc-b1-link.telia.net (62.115.123.206)  10.821 ms
 6  chi-b21-link.telia.net (62.115.139.20)  23.703 ms chi-b21-link.telia.net (62.115.125.153)  23.470 ms  23.493 ms
 7  shawbusiness-ic-300303-chi-b21.c.telia.net (62.115.12.82)  23.995 ms  23.958 ms shawbusiness-ic-157038-chi-b21.c.telia.net (62.115.9.78)  23.933 ms
 8  66.163.65.17 (66.163.65.17)  79.020 ms  79.497 ms  79.456 ms
 9  dx5ru-la0-s1.cg.int.shawcable.net (64.59.133.114)  53.829 ms  53.979 ms  53.747 ms

ive tested numerously and its very consistent.

Outcomes