Lol sure, save the salmon, got it.  I'll continue to have...

lum
Grasshopper

Lol sure, save the salmon, got it. 
I'll continue to have horrible ping, and wait for it to change to west servers.

0 Kudos
Reply
Loading...

I feel your pain; routings screwed as well for me in Edmo...

talios
Grasshopper

I feel your pain; routings screwed as well for me in Edmonton again making online gaming next to impossible . I feel like blaming it on the BC flooding is a cop out since it seems to happen every month or two with shaw these days; and as usual telus’ routing is completely  unaffected and routing as normal. If only Telus offered speeds higher than 50 mbps in my building 😞 

0 Kudos
Reply
Loading...

I'm in Alberta, left for a few days. When I got back all...

Mikec146
Grasshopper

I'm in Alberta, left for a few days. When I got back all of my routing was sent through Chicago, terrible ping on anything west coast, decent going to the east coast. Unfortunately I need that west coast ping. Tech support kept saying a connectivity issue, my connection seems completely fine, download speed upload speed etc, it's just routed to the wrong area. They have a technician coming in 4 days, was anybody able to resolve issues like this? Or should I start looking for a new provider?

0 Kudos
Reply
Loading...

I wonder what sending  a technician to your house will ac...

rstra
Grand Master

@Mikec146   I wonder what sending  a technician to your house will accomplish? If that is how Shaw routes, then the solution would be to try another provider.

0 Kudos
Reply
Loading...

-- Can you post some outputs from the Windows TRACERT com...

mdk
Legendary Grand Master

@Mikec146 -- Can you post some outputs from the Windows TRACERT command ?

For example, Greater Vancouver to a University in the Chicago area:

 

>> tracert www.loyola.edu.

Tracing route to www.loyola.edu [144.126.4.114]

 ....
4 11 ms 12 ms 12 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
5 36 ms 35 ms 34 ms rc3so-be82.cg.shawcable.net [66.163.76.10]
6 63 ms 64 ms 63 ms rc4ec-be13.il.shawcable.net [66.163.65.18]
7 * * * Request timed out.

namely Vancouver --> Calgary --> Illinois --> configured as a non-responding router

>> tracert www.uscs.edu

Tracing route to wcms-ucsc.prd.web.aws.ucsc.edu [128.114.119.88]
4 11 ms 11 ms 17 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
5 16 ms 14 ms 12 ms six.tr-cps.internet2.edu [206.81.80.77]
6 30 ms 29 ms 29 ms fourhundredge-0-0-0-19.4079.core1.seat.net.internet2.edu [163.253.1.158]
7 30 ms 29 ms 31 ms fourhundredge-0-0-0-0.4079.core1.sacr.net.internet2.edu [163.253.2.166]
8 30 ms 31 ms 29 ms fourhundredge-0-0-0-23.4079.core2.sacr.net.internet2.edu [163.253.1.39]
9 31 ms 29 ms 32 ms fourhundredge-0-0-0-0.4079.core2.sunn.net.internet2.edu [163.253.1.191]
10 29 ms 31 ms 30 ms 198.71.47.75
11 34 ms 30 ms 30 ms dc-ucsc--svl-agg8-10ge.cenic.net [137.164.3.49]

12 30 ms 29 ms 30 ms campus-south-fw1-v191.ucsc.edu [128.114.102.92]

13 313 ms 30 ms 29 ms core-south-g-v193.ucsc.edu [128.114.102.217]
14 29 ms 29 ms 30 ms dc2-g-e1-63.ucsc.edu [128.114.101.125]
15 29 ms 30 ms 30 ms vpn-dc.ucsc.edu [128.114.102.228]
16 30 ms 29 ms 31 ms resnet.ucsc.edu [128.114.119.88]

Vancouver --> Internet-2 --> Seattle --> Sacramento --> University of California @ Santa Cruz

Please show your results from Edmonton to the above sites, and also to your desired "west-coast" servers.

As @rstra implied, the routing over the Shaw "back-bone" is nothing that you (or a technician) can change, at your end.

Note that Shaw's back-bone has some redundancy, e.g., Edmonton -> Calgary -> USA, or Edmonton -> Winnipeg -> USA, or Edmonton -> Vancouver -> USA  So, if one "path" goes down, rerouting of your traffic falls-over to an alternate path.

 

 

 

0 Kudos
Reply
Loading...