Trust me, as someone who was given many service calls ove...

[rstra]

Trust me, as someone who was given many service calls over the years to “fix” a customers routing and latency issues, they don’t have a clue and neither do their supervisors. 

[kalamalka123]

same issue here in western Canada. used to get 40ms on dota 2 but 100ms now. 

[mdk]

@kalamalka123 -- same issue

Can you tell us where you live?

Can you use the Windows command-line utility: TRACERT to trace Internet packets from your IP-address to that "dota 2" game-server? With that information, there could be an explanation of the issue, rather than just a "me too" comment.

[kalamalka123]

Northern BC, I always use us-west server.

1 3 ms 3 ms 3 ms hitronhub.home 
2 * * * your request time is expired
3 56 ms 47 ms 55 ms rc2ar-be128-1.ed.shawcable.net [64.59.184.113]
4 76 ms 84 ms 167 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
5 86 ms 91 ms 92 ms rc3so-be110-1.cg.shawcable.net [66.163.76.61]
6 125 ms 127 ms 138 ms rc1wt-be82.wa.shawcable.net [66.163.76.9]
7 106 ms 109 ms 123 ms 66.163.64.58
8 * * * your request time is expired
9 * * * your request time is expired
10 * * * your request time is expired
11 * * * your request time is expired
12 144 ms 136 ms 168 ms eat.valve.net [192.69.96.1]

not sure what these mean....

[mdk]

@kalamalka123 -- Thanks for posting.

That trace gives the path for IP packets. Compare to intersections between highways, where you choose which road to take to get closer to your destination.

# / Time to send a packet to the destination, and get a reply  / name of a router / IP-address

3  55 ms rc2ar-be128-1.ed.shawcable.net [64.59.184.113] (Edmonton, on Shaw network)
4 167 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]        (Winnipeg, on Shaw network)
5   92 ms rc3so-be110-1.cg.shawcable.net [66.163.76.61]  (Calgary, on Shaw network)
6 138 ms rc1wt-be82.wa.shawcable.net [66.163.76.9]         (Vancouver, gateway to Washington State, on Shaw network)
7 123 ms 66.163.64.58                                                          (assigned to Shaw)        
8  * * * your request time is expired                                       (some routers are configured to NOT respond)

So, rather than the "usual" route from Shaw/Edmonton to Shaw/Calgary, a "detour" -- an alternate route -- (to Shaw/Winnipeg to Shaw/Calgary) has been used.

Just more evidence that something is wrong on that one segment.

Thanks.

[mdk]

@kalamalka123 ---

1 3 ms 3 ms 3 ms hitronhub.home 
2 * * * your request time is expired
3 56 ms 47 ms 55 ms rc2ar-be128-1.ed.shawcable.net [64.59.184.113]

Those numbers (milliseconds) from your HITRON to Shaw's router in ED(monton) are relatively high. That's not a good sign, for online gaming, unless you do the impossible: connect to a game-server in Edmonton. Only occasionally can the Edmonton Oilers give up a few goals in the 1st period, to "put them in a hole", and still recover to win the game -- a bad start implies an eventual defeat. Same goes for your "slow" connection to Edmonton.

[kalamalka123]

so this is the answer I got from an agent.

"yes its an offical known issue, Just reading the notes looks like there is parts inside the network that are needing to be replaced once that happens things should go back to normal. Potentially that could happen tonight. We are just waiting for the parts to arrive and be installed. I don't see an update for if the parts have arrived,"

[GBLawlz]

I'm in Winnipeg, I noticed a change in regular ping times about a week ago to Chicago. I'm one of those weird people that is very aware of what my regular pings should be to certain locations. I have done as much troubleshooting as a simple end client can to see where the increase is happening. Unlike some of the others here, my ping increase was "stable", as in it is constantly 7-9MS higher, at all times of the day. This is for everything that is routed to, or through Chicago. Tested this with Shaw connections from multiple locations in Winnipeg, including my work office with business Shaw (docsis still). This rules out individual neighborhoods in theory. 

I regularly ping google DNS (8.8.8.8) which is in Chicago to test ping times, and have been for years. Normal for a wired Shaw connection in WPG is 22-23MS. My buddy on BellMTS FTTH gets 17-18MS to the same spot. Thats good and normal, essentially same response time once it leaves the home (minus the docsis link delay of 5-7MS). Guy on BellMTS is NOT affected by what's going on with Shaw. So this is 100% within Shaw's network environment. 

For the last week I now regularly get 31-33MS to the same 8.8.8.8. I'll put a trace that shows on which hop we're seeing the increase. 

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 10 ms 10 ms 10 ms 50.71.0.1
3 13 ms 15 ms 12 ms rc3sc-be124-1.wp.shawcable.net [64.59.178.201]
4 35 ms 33 ms 34 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134]  <---- Here is where the extra latency is being introduced. Normally this is 22-24MS
5 33 ms 31 ms 33 ms rc4ec-tge0-0-0-5.il.shawcable.net [66.163.65.14]
6 34 ms 35 ms 36 ms 74.125.251.147
7 36 ms 35 ms 34 ms 216.239.42.33
8 35 ms 36 ms 33 ms dns.google [8.8.8.8]

Trace complete.

Something changed about a week ago with something to do with how traffic is leaving Winnipeg and going to Chicago. This obviously affects neighboring provinces to MB, since WPG > CHI is a major exit point into the US.   

My guess is some hardware, either in Winnipeg, or somewhere along the fiber route to Chicago has either failed or is being upgraded. This is having all the traffic jump onto older crappier backup equipment within that data center environment. I just wish in these situations Shaw would put out a bulletin to its tech support people so when we call and ask these very technical questions we get a reason why. I'd rather know that something is being fixed, and it will be another 1-2 weeks VS try restarting your computer, modem and update anti virus.  

[mdk]

@GBLawlz -- Something changed about a week ago with something to do with how traffic is leaving Winnipeg and going to Chicago. 

What seems to have changed is that the Shaw "backbone" segment between Calgary and Edmonton is not functioning.

So, all traffic between those two cities is going through the segments from Edmonton to Winnipeg, or Winnipeg to Calgary.

Edmonton is a major "hub" for Shaw. As a "hub", it carries all the Shaw traffic from northeastern British Columbia, and all the traffic from Saskatoon (and vicinity), in addition to all the traffic from the Edmonton area.

Pity that poor overworked Shaw router in Winnipeg -- suddenly being required to handle a lot of traffic that normally would go from Edmonton to Vancouver to Seattle, and beyond, because it is now handling "double" the traffic on the segment from Winnipeg to Chicago.

[j0l0]

I'm just jumping in here as I am having the same issue. I live in the Edmonton area and normally gaming has been top notch on my connection. As of late, it has been abysmal. I have done the tracert as you mentioned and everything is routing through Winnipeg as suspected. 

Tracing route to ubc.ca [206.87.224.15]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 10 ms 9 ms 10 ms 68.149.160.1
3 10 ms 9 ms 10 ms rc2ar-be136-1.ed.shawcable.net [64.59.185.49]
4 12 ms 11 ms 10 ms 24.244.59.129
5 10 ms 14 ms 10 ms 24.244.60.53
6 10 ms 10 ms 10 ms rc2ar-be212.ed.shawcable.net [24.244.58.117]
7 25 ms 24 ms 24 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
8 39 ms 42 ms 40 ms rc3so-be110-1.cg.shawcable.net [66.163.76.61]
9 50 ms 50 ms 50 ms rc1bb-be6-1.vc.shawcable.net [66.163.78.38]
10 * * * Request timed out.
11 51 ms 50 ms 51 ms 64.251.87.210
12 53 ms 52 ms 51 ms 134.87.30.149
13 66 ms 67 ms 69 ms 137.82.88.122
14 67 ms 70 ms 69 ms a22-a0.net.ubc.ca [137.82.123.113]
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.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Tracing route to www.ucalgary.ca [136.159.96.125]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 10 ms 13 ms 8 ms 68.149.160.1
3 10 ms 9 ms 9 ms rc2ar-be136-1.ed.shawcable.net [64.59.185.49]
4 13 ms 16 ms 10 ms 24.244.59.129
5 10 ms 10 ms 15 ms 24.244.60.53
6 9 ms 10 ms 10 ms rc2ar-be212.ed.shawcable.net [24.244.58.117]
7 27 ms 25 ms 24 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
8 39 ms 44 ms 46 ms rc3so-be110-1.cg.shawcable.net [66.163.76.61]
9 * * * Request timed out.
10 48 ms 40 ms 46 ms fw1uofc.cg.bigpipeinc.com [206.174.203.106]
11 40 ms 39 ms 39 ms h66-244-233-20.bigpipeinc.com [66.244.233.20]
12 48 ms 47 ms 38 ms h77.gpvpn.ucalgary.ca [136.159.199.77]
13 39 ms 39 ms 38 ms 10.59.226.25
14 * * * Request timed out.
15 43 ms 39 ms 46 ms 10.17.184.1
16 41 ms 39 ms 45 ms braincreate.ca [136.159.96.125]

Tracing route to www.usask.ca [128.233.198.150]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 11 ms 10 ms 9 ms 68.149.160.1
3 11 ms 10 ms 10 ms rc2ar-be136-1.ed.shawcable.net [64.59.185.49]
4 10 ms 10 ms 11 ms 24.244.59.129
5 15 ms 11 ms 10 ms 24.244.60.53
6 9 ms 11 ms 10 ms rc2ar-be212.ed.shawcable.net [24.244.58.117]
7 24 ms 24 ms 29 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
8 39 ms 41 ms 40 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134]
9 40 ms 39 ms 41 ms 10gigabitethernet4-1.core1.chi1.he.net [208.115.136.37]
10 52 ms 62 ms 47 ms 100ge14-2.core1.msp1.he.net [184.105.223.178]
11 95 ms 86 ms 56 ms 100ge10-1.core1.ywg1.he.net [184.105.64.86]
12 64 ms 65 ms 65 ms 100ge5-2.core1.yxe1.he.net [184.104.192.70]
13 65 ms 69 ms 65 ms 66.220.3.186
14 65 ms 64 ms 68 ms 128.233.16.2
15 * * * Request timed out.
16 64 ms 65 ms 64 ms www.usask.ca [128.233.198.150]

Tracing route to www.uwinnipeg.ca [72.2.13.34]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 11 ms 11 ms 9 ms 68.149.160.1
3 10 ms 12 ms 9 ms rc2ar-be136-1.ed.shawcable.net [64.59.185.49]
4 12 ms 11 ms 10 ms 24.244.59.129
5 11 ms 9 ms 10 ms 24.244.60.53
6 16 ms 17 ms 9 ms rc2ar-be212.ed.shawcable.net [24.244.58.117]
7 28 ms 25 ms 25 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
8 26 ms 25 ms 28 ms rc2nr-tge0-11-0-10.wp.shawcable.net [66.163.73.150]
9 26 ms 32 ms 26 ms h64-141-108-237.bigpipeinc.com [64.141.108.237]
10 26 ms 25 ms 26 ms h64-141-108-131.bigpipeinc.com [64.141.108.131]
11 29 ms 25 ms 25 ms www.uwinnipeg.ca [72.2.13.34]

Tracing route to google.ca [172.217.4.195]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 11 ms 8 ms 8 ms 68.149.160.1
3 12 ms 10 ms 10 ms rc2ar-be136-1.ed.shawcable.net [64.59.185.49]
4 11 ms 10 ms 10 ms 24.244.59.129
5 10 ms 10 ms 10 ms 24.244.60.53
6 11 ms 10 ms 11 ms rc2ar-be212.ed.shawcable.net [24.244.58.117]
7 27 ms 30 ms 26 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
8 42 ms 41 ms 40 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134]
9 40 ms 45 ms 42 ms rc4ec-tge0-0-0-5.il.shawcable.net [66.163.65.14]
10 43 ms 41 ms 42 ms 209.85.240.245
11 41 ms 40 ms 40 ms 74.125.251.47
12 41 ms 41 ms 39 ms ord37s19-in-f3.1e100.net [172.217.4.195]

Hopefully this gets resolved soon.