AnsweredAssumed Answered

Can someone at shaw please look into or explain why connections to seattle are running through chicago?

Question asked by joshua93 on Nov 10, 2016
Latest reply on Nov 16, 2016 by dpsi

Can someone at shaw please look into or explain why connections to seattle are running through chicago?

I remember the days when it used to be 29~ ms.

 

traceroute to [my_server_in_seattle] ([server ip addr]), 64 hops max, 52 byte packets

1  192.168.1.1 (192.168.1.1)  126.139 ms  0.824 ms  0.597 ms

2  68.147.160.1 (68.147.160.1)  17.480 ms  9.006 ms  8.660 ms

3  rc3so-be104-1.cg.shawcable.net (64.59.131.185)  9.944 ms  10.364 ms  10.553 ms

4  rc4ec-be13.il.shawcable.net (66.163.65.18)  39.972 ms

5  rc3ec-hge0-9-0-1.il.shawcable.net (66.163.65.109)  49.851 ms

 

6  xe-11-2-1.chi11.ip4.gtt.net (199.229.230.229)  59.963 ms

 

7  et-2-1-0.cr3-sea2.ip4.gtt.net (141.136.110.193)  90.445 ms  92.235 ms  100.951 ms

8  * * *

9  * * *

10  [my_server_in_seattle] ([server ip addr])  91.723 ms  89.942 ms  103.139 ms

Outcomes