Packet Loss at Shaw router/node

[SKim2]

I have noticed a packet loss of up to 5% at one of Shaw nodes/router.

I have notice it is consistently one of the node(24.244.58.49) that shows packet loss.

This can be observed with traceroute.

Wonder how I can notify one of the network engineer to have a look at the node or provide an explanation.

Thanks.

[mdk]

@SKim2 -- welcome to this peer-to-peer discussion forum. It is NOT a direct path to Shaw Support.

Contact Shaw Support: 

• 1-888-472-2222
• www.shaw.ca/chat
• if neither of the above work for you, scroll-down while reading this reply, and click on the "Your Voice" hyperlink

P.S. Many Shaw routers have IP-addresses ending with ".1". I think that it is unusual to see ".49", but not impossible.

For me, "traceroute" shows no issue:

$  ping -n 10 24.244.58.49

Pinging 24.244.58.49 with 32 bytes of data:
Reply from 24.244.58.49: bytes=32 time=15ms 
Reply from 24.244.58.49: bytes=32 time=13ms 
Reply from 24.244.58.49: bytes=32 time=10ms 
Reply from 24.244.58.49: bytes=32 time=9ms 
Reply from 24.244.58.49: bytes=32 time=10ms 
Reply from 24.244.58.49: bytes=32 time=9ms 
Reply from 24.244.58.49: bytes=32 time=9ms 
Reply from 24.244.58.49: bytes=32 time=9ms 
Reply from 24.244.58.49: bytes=32 time=10ms 
Reply from 24.244.58.49: bytes=32 time=9ms 

Ping statistics for 24.244.58.49:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Can you please post the output from your trace?

[SKim2]

I use mtr rather than traceroute which provided live update.

Here is a screenshot:

[mdk]

@SKim2 -- note that routers can be configured to give lower priority to "overhead" packets (PING, TraceRoute) and higher priority to "useful" packets.  In your output, that ".221" Shaw router in Vancouver seems to be "busier" (Worst=182, StandardDeviation=18.1) than any of the other Shaw (and Google) routers.

Are you noticing any actual problems when connecting to Google? Is 4.8% so bad that you cannot use Google?

Is it still happening?  I see:

Tracing route to www.google.com [142.250.217.100]
...

5 59 ms 13 ms 12 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
6 13 ms 12 ms 17 ms 72.14.221.102
7 60 ms 70 ms 13 ms 108.170.245.97
8 12 ms 14 ms 12 ms 142.251.55.201
9 11 ms 12 ms 10 ms sea09s30-in-f4.1e100.net [142.250.217.100]

Trace complete.

Reply from 142.250.217.100: bytes=32 time=14ms 
Reply from 142.250.217.100: bytes=32 time=20ms 
Reply from 142.250.217.100: bytes=32 time= 9ms 
Reply from 142.250.217.100: bytes=32 time= 9ms 
Reply from 142.250.217.100: bytes=32 time=10ms 
Reply from 142.250.217.100: bytes=32 time=10ms 
Reply from 142.250.217.100: bytes=32 time= 9ms 
Reply from 142.250.217.100: bytes=32 time=10ms 
Reply from 142.250.217.100: bytes=32 time=10ms 
Reply from 142.250.217.100: bytes=32 time= 9ms 

Ping statistics for 142.250.217.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

This seems to be a "clean" connection.

[SKim2]

I notice packet loss when playing Valorant.

I initially checked using Riot games server. It had the same problem on the same Shaw node.

I just used google because its more convient that looking up Riot game server.

See post from Reddit few one day ago.

https://www.reddit.com/r/shaw/comments/wbpdov/high_ping/