1. Are you able to use a tool like mtr (instead of traceroute), so the loss can be tracked back to a specific hop easier? mtr is also ICMP-based unless otherwise specified. I want to believe it's between hop #6 and #7 but I cannot rule out what's shown at hop #1, nor do I know if the loss shown at #7 is normal or not. If you need to know what mtr flags to use, I recommend -4 -z -b --order=LSRNABW
2. This is only half the picture due to asymmetric routing being common. Are you able to run mtr on/from the destination (208.79.93.154) going back to the source (whatever your IP is)? Ideally, start both mtrs at the same time + let them run for a full 5-10 minutes; anything less isn't helpful. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administrator PGP 0x2A389531 | | Making life hard for others since 1977. | On Mon, Jan 15, 2024 at 11:12:28AM -0800, Lyndon Nerenberg (VE7TFX/VE6BBM) via Outages wrote: > For the last hour I've been seeing high packet loss rates inside > Shaw's western Canada network. E.g.: > > --- orthanc.ca ping statistics --- > 152 packets transmitted, 8 packets received, 94.7% packet loss > round-trip min/avg/max/stddev = 109.441/285.678/696.621/194.853 ms > > That's from Vancouver residential to a colo server in L.A. A typical > traceroute shows the choke point seems to be Calgary: > > traceroute to orthanc.ca (208.79.93.154), 64 hops max, 72 byte packets > 1 * 192.168.0.1 (192.168.0.1) 20.742 ms 4.571 ms > 2 24.86.192.1 (24.86.192.1) 15.915 ms 12.080 ms 16.014 ms > 3 rc1bb-be147-1.vc.shawcable.net (64.59.150.185) 11.852 ms 16.537 ms > 31.073 ms > 4 24.244.59.217 (24.244.59.217) 12.509 ms 12.295 ms 12.035 ms > 5 24.83.252.66 (24.83.252.66) 11.529 ms 24.933 ms 197.457 ms > 6 rc1st-be214.vc.shawcable.net (24.244.58.65) 13.587 ms 10.923 ms > 104.439 ms > 7 * * rc3no-be11-1.cg.shawcable.net (66.163.72.69) 58.938 ms > 8 rc3so-be23.cg.shawcable.net (66.163.71.118) 50.948 ms 27.276 ms 25.755 > ms > 9 66.163.71.42 (66.163.71.42) 24.937 ms 30.755 ms 23.542 ms > 10 rc4ec-be13.il.shawcable.net (66.163.65.18) 96.292 ms * 90.125 ms > 11 equinix-ch2.cr2.ord1.amcbb.net (208.115.136.124) 53.652 ms * * > 12 ae1-4.cr1.ord1.atlanticmetro.net (174.128.183.2) 173.172 ms * 248.078 ms > 13 ve521.cr2.lax0.atlanticmetro.net (208.78.26.210) 126.758 ms * * > 14 xe-0-0-3-0.cr2.lax2.atlanticmetro.net (208.78.31.37) 104.574 ms 234.672 > ms * > 15 * ae3-4.cr2.lax3.atlanticmetro.net (173.205.176.40) 114.315 ms * > 16 arpnetworks-dmarc.lax3.atlanticmetro.net (173.205.184.132) 179.245 ms * * > 17 * orthanc.ca (208.79.93.154) 191.936 ms 102.680 ms > > Anyone else seeing this? Or know what's going on? > > --lyndon > _______________________________________________ > Outages mailing list > Outages@outages.org > https://puck.nether.net/mailman/listinfo/outages > _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages