I've had 3 Rogers techs sent out, one who replaced the gateway and another which identified it as a "neighborhood node issue" and said technicians would be sent to make some adjustments to the neighborhood node. For several hours each day, the latency seems to be horrendous but speeds seem OK in general. Very disruptive to work from home / gaming / video calls... Any advice?
Below is an example where I was just pinging google.com repeatedly. Also note: results are the same on ethernet vs wifi and bridged mode with my own router vs Rogers gateway. I've also tried the regular troubleshooting steps (power cycling, modem on it's on electrical outlet, different locations for the modem, etc.).
Ping Example
Thu, Jun 1, 2023 8:45:43 PM - Reply from 142.251.41.46: bytes=32 time=64ms TTL=118
Thu, Jun 1, 2023 8:45:44 PM - Reply from 142.251.41.46: bytes=32 time=71ms TTL=118
Thu, Jun 1, 2023 8:45:46 PM - Reply from 142.251.41.46: bytes=32 time=941ms TTL=118
Thu, Jun 1, 2023 8:45:46 PM - Reply from 142.251.41.46: bytes=32 time=207ms TTL=118
Thu, Jun 1, 2023 8:45:48 PM - Reply from 142.251.41.46: bytes=32 time=715ms TTL=118
Thu, Jun 1, 2023 8:45:48 PM - Reply from 142.251.41.46: bytes=32 time=95ms TTL=118
Thu, Jun 1, 2023 8:45:49 PM - Reply from 142.251.41.46: bytes=32 time=55ms TTL=118
Thu, Jun 1, 2023 8:45:51 PM - Reply from 142.251.41.46: bytes=32 time=1231ms TTL=118
Thu, Jun 1, 2023 8:45:51 PM - Reply from 142.251.41.46: bytes=32 time=15ms TTL=118
Thu, Jun 1, 2023 8:45:53 PM - Reply from 142.251.41.46: bytes=32 time=859ms TTL=118
Thu, Jun 1, 2023 8:45:54 PM - Reply from 142.251.41.46: bytes=32 time=40ms TTL=118
Thu, Jun 1, 2023 8:45:55 PM - Reply from 142.251.41.46: bytes=32 time=186ms TTL=118
Thu, Jun 1, 2023 8:45:56 PM - Reply from 142.251.41.46: bytes=32 time=116ms TTL=118
Thu, Jun 1, 2023 8:45:57 PM - Reply from 142.251.41.46: bytes=32 time=32ms TTL=118
Thu, Jun 1, 2023 8:46:01 PM - Reply from 142.251.41.46: bytes=32 time=3130ms TTL=118
Thu, Jun 1, 2023 8:46:01 PM - Reply from 142.251.41.46: bytes=32 time=19ms TTL=118
Thu, Jun 1, 2023 8:46:02 PM - Reply from 142.251.41.46: bytes=32 time=301ms TTL=118
Thu, Jun 1, 2023 8:46:03 PM - Reply from 142.251.41.46: bytes=32 time=26ms TTL=118
Thu, Jun 1, 2023 8:46:04 PM - Reply from 142.251.41.46: bytes=32 time=64ms TTL=118
Thu, Jun 1, 2023 8:46:05 PM - Reply from 142.251.41.46: bytes=32 time=136ms TTL=118
Thu, Jun 1, 2023 8:46:06 PM - Reply from 142.251.41.46: bytes=32 time=568ms TTL=118
Thu, Jun 1, 2023 8:46:08 PM - Reply from 142.251.41.46: bytes=32 time=1081ms TTL=118
Thu, Jun 1, 2023 8:46:08 PM - Reply from 142.251.41.46: bytes=32 time=82ms TTL=118
Thu, Jun 1, 2023 8:46:09 PM - Reply from 142.251.41.46: bytes=32 time=15ms TTL=118
Thu, Jun 1, 2023 8:46:12 PM - Reply from 142.251.41.46: bytes=32 time=1890ms TTL=118
Thu, Jun 1, 2023 8:46:12 PM - Reply from 142.251.41.46: bytes=32 time=13ms TTL=118
Thu, Jun 1, 2023 8:46:13 PM - Reply from 142.251.41.46: bytes=32 time=12ms TTL=118
Thu, Jun 1, 2023 8:46:16 PM - Reply from 142.251.41.46: bytes=32 time=2218ms TTL=118
Thu, Jun 1, 2023 8:46:16 PM - Reply from 142.251.41.46: bytes=32 time=14ms TTL=118
Thu, Jun 1, 2023 8:46:18 PM - Reply from 142.251.41.46: bytes=32 time=609ms TTL=118
Thu, Jun 1, 2023 8:46:19 PM - Reply from 142.251.41.46: bytes=32 time=1001ms TTL=118
Thu, Jun 1, 2023 8:46:19 PM - Reply from 142.251.41.46: bytes=32 time=20ms TTL=118
Thu, Jun 1, 2023 8:46:20 PM - Reply from 142.251.41.46: bytes=32 time=9ms TTL=118
Thu, Jun 1, 2023 8:46:21 PM - Reply from 142.251.41.46: bytes=32 time=21ms TTL=118
Thu, Jun 1, 2023 8:46:23 PM - Reply from 142.251.41.46: bytes=32 time=1416ms TTL=118
Thu, Jun 1, 2023 8:46:23 PM - Reply from 142.251.41.46: bytes=32 time=15ms TTL=118
Traceroutes (note: conducted with ethernet to external router + gateway in bridge mode, but results are same on ethernet to gateway).
(Worst case in 5 runs)
Tracing route to google.ca [142.251.32.67] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms GT-AXE11000-1970 [192.168.50.1]
2 57 ms 67 ms 69 ms 99.229.50.1
3 338 ms 51 ms 88 ms 24.156.143.129
4 641 ms 473 ms 2248 ms 3021-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.232.49]
5 73 ms 44 ms 88 ms 209.148.235.222
6 * * * Request timed out.
7 36 ms 32 ms 39 ms 74.125.244.145
8 15 ms 15 ms 31 ms 142.251.68.25
9 60 ms 14 ms 39 ms yyz12s07-in-f3.1e100.net [142.251.32.67]
(Worst case in 5 runs)
Tracing route to dns.google [8.8.8.8] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms GT-AXE11000-1970 [192.168.50.1]
2 64 ms 16 ms 138 ms 99.229.50.1
3 57 ms 37 ms 12 ms 24.156.143.133
4 29 ms 23 ms 20 ms 3201-cgw01.wlfdle.rmgt.net.rogers.com [209.148.232.53]
5 14 ms 24 ms 59 ms 209.148.235.214
6 130 ms 36 ms 31 ms 72.14.216.54
7 17 ms 35 ms 45 ms 108.170.250.241
8 214 ms 154 ms 51 ms 172.253.69.113
9 2781 ms 598 ms 188 ms dns.google [8.8.8.8]
(Median case in 5 runs)
Tracing route to dns.google [8.8.8.8] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms GT-AXE11000-1970 [192.168.50.1]
2 33 ms 30 ms 41 ms 99.229.50.1
3 15 ms 24 ms 38 ms 24.156.143.133
4 73 ms 39 ms 33 ms 3201-cgw01.wlfdle.rmgt.net.rogers.com [209.148.232.53]
5 31 ms 51 ms 38 ms 209.148.235.214
6 50 ms 24 ms 17 ms 72.14.216.54
7 37 ms 23 ms 17 ms 108.170.250.241
8 93 ms 43 ms 33 ms 172.253.69.113
9 39 ms 25 ms 25 ms dns.google [8.8.8.8]
I've enjoyed my experience with Rogers so far, but this is becoming unacceptable for daily use... 😢
