I'm having this exact same issue. Connecting to the Orego...

[TK11]

I'm having this exact same issue. Connecting to the Oregon server on Valorant is usually 40ms, now it's 120ms. When I do a tracert it shows the connection being routed through Chicago, instead of the normal path through Vancouver. If this isn't resolved I'll have to cancel my services.

[Shanty]

Same issue. After running multiple traces, the problems seems to be on Shaw's end. After talking to costumer support, they're aware of the issues but were only able to offer a hard reset at this time, which sadly did nothing.

[TK11]

Microsoft Windows [Version 10.0.19041.867]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\xxxxx>tracert oregeon.gov
Unable to resolve target system name oregeon.gov.

C:\Users\xxxxx>tracert oregon.gov

Tracing route to oregon.gov [63.241.205.31]
over a maximum of 30 hops:

1 2 ms 2 ms 3 ms 10.0.0.1
2 11 ms 11 ms 10 ms 96.52.64.1
3 11 ms 11 ms 10 ms rc2ar-be105-1.ed.shawcable.net [64.59.186.57]
4 11 ms 12 ms 12 ms 24.244.59.165
5 14 ms 16 ms 13 ms 24.244.60.49
6 9 ms 12 ms 11 ms rc2ar-be212.ed.shawcable.net [24.244.58.117]
7 27 ms 28 ms 27 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
8 60 ms 57 ms 56 ms rc3so-be110-1.cg.shawcable.net [66.163.76.61]
9 62 ms 54 ms 55 ms rc4ec-be13.il.shawcable.net [66.163.65.18]
10 90 ms 89 ms 87 ms chi-b23-link.ip.twelve99.net [213.248.75.194]
11 87 ms 88 ms 88 ms chi-b2-link.ip.twelve99.net [62.115.122.195]
12 109 ms 111 ms 111 ms att-ic155020-chi-b2.ip.twelve99-cust.net [213.248.87.254]
13 116 ms 116 ms 118 ms cr2.cgcil.ip.att.net [12.122.132.198]
14 114 ms 118 ms 118 ms sl9mo22crs.ip.att.net [12.122.2.178]
15 106 ms 110 ms 102 ms sl9mo21crs.ip.att.net [12.122.2.217]
16 116 ms 118 ms 118 ms dlstx22crs.ip.att.net [12.122.2.1]
17 97 ms 97 ms 98 ms 12.123.18.241
18 115 ms 115 ms 114 ms 32.130.248.198
19 122 ms 116 ms 115 ms 32.130.248.207
20 98 ms 97 ms 98 ms 63.241.203.182
21 115 ms 113 ms 113 ms 63.241.232.22
22 100 ms 100 ms 102 ms or-prd-moss-txdc.cdc.nicusa.com [63.241.205.31]

Trace complete.

Here's a tracert to a Texas server. You can see it goes from Calgary, directly to this IP 213.248.75.194 in Chicago. It usually goes to Vancouver first.

[TK11]

This isnt an issue with Riot Games. This is happening on Apex, Counter Strike, Rocket League and Call of Duty.

[Shanty]

Any update on a fix to this? The problem for everyone seems to be routing it randomly to a server in Chicago which wasn’t the case two-three days ago.

This isn’t just one game, and is on Shaw’s end as tracing has showed.

[norkieman]

im in Thunder Bay and route thru Winnipeg Shaw and everyone i know who has shaw here has had ridiculous pings for the last 6 days or so

usually 35 CHI now 60-65 CHI 

texas is usually 55-60 now its 80+

this goes for CSGO and Valorant.. any game actually but those are the two i play/checked. This has happened 2 times since i had to switch to shaw last September but was resolved in 1-2 weeks.. still nothing yet here.

This is 100% an issue on Shaws end

[TK11]

All of Western Canada is now routing through your servers, there's a traffic jam lol

[mdk]

@TK11 -- tracing from the Shaw network from the Vancouver (BC) area to "Oregon.gov", I see:

12 ms  rc1wt-be40.wa.shawcable.net [66.163.68.18]
12 ms  be4476.ccr21.sea02.atlas.cogentco.com [38.88.252.161]
15 ms  att.sea02.atlas.cogentco.com [154.54.11.106]
63 ms  st0wa81crs.ip.att.net [12.122.158.162]
64 ms  st6wa22crs.ip.att.net [12.122.111.110]
63 ms  dvmco22crs.ip.att.net [12.122.2.157]
63 ms  dlstx22crs.ip.att.net [12.122.2.85]
56 ms  12.123.18.241
56 ms  32.130.248.200
56 ms  32.130.248.223
57 ms  63.241.203.182
59 ms  63.241.232.22
56 ms  or-prd-moss-txdc.cdc.nicusa.com [63.241.205.31]

namely, Vancouver -> Seattle -> "WA22" -> "CO22" (maybe, Cornwallis suburb of Portland Oregon) -> T(ransit) e(X)change -> AT&T routers -> fast web-hosting supplied by a Texas-based company.

So, it could be the Shaw routers: Edmonton -> Winnipeg -> Calgary -> Chicago that have routing-tables that do not "prefer" a direct connection from Edmonton to Calgary. Maybe, that direct route is temporarily "unavailable" ???

[mdk]

@TK11 -- This is not an issue with Riot Games.

VALORANT is supplied by RIOT GAMES.

> This is happening on Apex, Counter Strike, Rocket League and Call of Duty.

What are the IP-addresses for those servers? Can you use TRACERT to each IP-address?

If all of those IP-addresses are routed from Edmonton -> Winnipeg -> Calgary -> somewhere

then all of them probably will have lesser performance when the direct route from Edmonton -> Calgary is temporarily not available.

[mdk]

@Shanty -- Any update on a fix to this? 

Welcome to this peer-to-peer discussion forum. It is not a path to Shaw Support.

So, nobody here is authorized to speak on behalf of Shaw, to answer your question.

Please contact Shaw ( www.shaw.ca/chat ) or 1-888-472-2222, to communicate with Shaw.