11-14-2022 11:17 AM
So I switched over from Bell to Rogers and I keep getting these frequent disconnects and reconnect to the internet. I ran a ping test and trace route which can be found below. I had a rogers technician switch out the modem but that did not solve the problem and I'm still getting these disconnects and reconnects.
64 bytes from 172.217.13.132: icmp_seq=0 ttl=117 time=8.396 ms
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
64 bytes from 172.217.13.132: icmp_seq=10 ttl=117 time=10.857 ms
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
64 bytes from 172.217.13.132: icmp_seq=13 ttl=117 time=9.298 ms
64 bytes from 172.217.13.132: icmp_seq=14 ttl=117 time=9.934 ms
64 bytes from 172.217.13.132: icmp_seq=15 ttl=117 time=9.684 ms
64 bytes from 172.217.13.132: icmp_seq=16 ttl=117 time=11.365 ms
64 bytes from 172.217.13.132: icmp_seq=17 ttl=117 time=12.289 ms
64 bytes from 172.217.13.132: icmp_seq=18 ttl=117 time=10.713 ms
64 bytes from 172.217.13.132: icmp_seq=19 ttl=117 time=12.019 ms
64 bytes from 172.217.13.132: icmp_seq=20 ttl=117 time=14.906 ms
64 bytes from 172.217.13.132: icmp_seq=21 ttl=117 time=10.925 ms
64 bytes from 172.217.13.132: icmp_seq=22 ttl=117 time=12.859 ms
64 bytes from 172.217.13.132: icmp_seq=23 ttl=117 time=8.421 ms
64 bytes from 172.217.13.132: icmp_seq=24 ttl=117 time=9.657 ms
64 bytes from 172.217.13.132: icmp_seq=25 ttl=117 time=13.013 ms
64 bytes from 172.217.13.132: icmp_seq=26 ttl=117 time=11.254 ms
64 bytes from 172.217.13.132: icmp_seq=27 ttl=117 time=11.102 ms
64 bytes from 172.217.13.132: icmp_seq=28 ttl=117 time=10.929 ms
64 bytes from 172.217.13.132: icmp_seq=29 ttl=117 time=14.069 ms
64 bytes from 172.217.13.132: icmp_seq=30 ttl=117 time=14.091 ms
64 bytes from 172.217.13.132: icmp_seq=31 ttl=117 time=10.980 ms
64 bytes from 172.217.13.132: icmp_seq=32 ttl=117 time=11.224 ms
64 bytes from 172.217.13.132: icmp_seq=33 ttl=117 time=8.544 ms
64 bytes from 172.217.13.132: icmp_seq=34 ttl=117 time=11.183 ms
64 bytes from 172.217.13.132: icmp_seq=35 ttl=117 time=10.842 ms
64 bytes from 172.217.13.132: icmp_seq=36 ttl=117 time=11.765 ms
64 bytes from 172.217.13.132: icmp_seq=37 ttl=117 time=11.837 ms
64 bytes from 172.217.13.132: icmp_seq=38 ttl=117 time=12.453 ms
64 bytes from 172.217.13.132: icmp_seq=39 ttl=117 time=9.017 ms
64 bytes from 172.217.13.132: icmp_seq=40 ttl=117 time=10.451 ms
64 bytes from 172.217.13.132: icmp_seq=41 ttl=117 time=11.116 ms
64 bytes from 172.217.13.132: icmp_seq=42 ttl=117 time=10.852 ms
64 bytes from 172.217.13.132: icmp_seq=43 ttl=117 time=9.126 ms
64 bytes from 172.217.13.132: icmp_seq=44 ttl=117 time=11.537 ms
64 bytes from 172.217.13.132: icmp_seq=45 ttl=117 time=12.986 ms
64 bytes from 172.217.13.132: icmp_seq=46 ttl=117 time=10.178 ms
64 bytes from 172.217.13.132: icmp_seq=47 ttl=117 time=9.498 ms
64 bytes from 172.217.13.132: icmp_seq=48 ttl=117 time=14.648 ms
64 bytes from 172.217.13.132: icmp_seq=49 ttl=117 time=11.515 ms
--- www.google.com ping statistics ---
50 packets transmitted, 39 packets received, 22.0% packet loss
round-trip min/avg/max/stddev = 8.396/11.168/14.906/1.623 ms
Of note for the ping test, I ran a longer test and encountered these lines (again, pinged to www.google.com😞
64 bytes from 172.217.13.164: icmp_seq=186 ttl=117 time=13.185 ms
64 bytes from 172.217.13.164: icmp_seq=187 ttl=117 time=11.563 ms
64 bytes from 172.217.13.164: icmp_seq=188 ttl=117 time=11.533 ms
64 bytes from 172.217.13.164: icmp_seq=189 ttl=117 time=12.705 ms
64 bytes from 172.217.13.164: icmp_seq=190 ttl=117 time=15.812 ms
64 bytes from 172.217.13.164: icmp_seq=191 ttl=117 time=12.775 ms
64 bytes from 172.217.13.164: icmp_seq=192 ttl=117 time=11.271 ms
64 bytes from 172.217.13.164: icmp_seq=193 ttl=117 time=11.928 ms
64 bytes from 172.217.13.164: icmp_seq=194 ttl=117 time=12.921 ms
64 bytes from 172.217.13.164: icmp_seq=195 ttl=117 time=19.894 ms
64 bytes from 172.217.13.164: icmp_seq=196 ttl=117 time=11.889 ms
64 bytes from 172.217.13.164: icmp_seq=197 ttl=117 time=12.000 ms
64 bytes from 172.217.13.164: icmp_seq=198 ttl=117 time=13.488 ms
64 bytes from 172.217.13.164: icmp_seq=199 ttl=117 time=12.222 ms
64 bytes from 172.217.13.164: icmp_seq=200 ttl=117 time=10.210 ms
64 bytes from 172.217.13.164: icmp_seq=201 ttl=117 time=13.527 ms
64 bytes from 172.217.13.164: icmp_seq=202 ttl=117 time=7.657 ms
Request timeout for icmp_seq 203
Request timeout for icmp_seq 204
Request timeout for icmp_seq 205
Request timeout for icmp_seq 206
Request timeout for icmp_seq 207
Request timeout for icmp_seq 208
Request timeout for icmp_seq 209
Request timeout for icmp_seq 210
Request timeout for icmp_seq 211
Request timeout for icmp_seq 212
Request timeout for icmp_seq 213
Request timeout for icmp_seq 214
Request timeout for icmp_seq 215
Request timeout for icmp_seq 216
Request timeout for icmp_seq 217
Request timeout for icmp_seq 218
Request timeout for icmp_seq 219
Request timeout for icmp_seq 220
92 bytes from cpe18593394b320-cm18593394b31d.cpe.net.cable.rogers.com (173.35.38.75): Destination Host Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 0758 0 0000 3f 01 af60 10.0.0.116 172.217.13.164
92 bytes from cpe18593394b320-cm18593394b31d.cpe.net.cable.rogers.com (173.35.38.75): Destination Host Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 a728 0 0000 3f 01 0f90 10.0.0.116 172.217.13.164
92 bytes from cpe18593394b320-cm18593394b31d.cpe.net.cable.rogers.com (173.35.38.75): Destination Host Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 2953 0 0000 3f 01 8d65 10.0.0.116 172.217.13.164
Request timeout for icmp_seq 221
64 bytes from 172.217.13.164: icmp_seq=222 ttl=117 time=12.955 ms
64 bytes from 172.217.13.164: icmp_seq=223 ttl=117 time=11.729 ms
64 bytes from 172.217.13.164: icmp_seq=224 ttl=117 time=8.253 ms
64 bytes from 172.217.13.164: icmp_seq=225 ttl=117 time=12.856 ms
64 bytes from 172.217.13.164: icmp_seq=226 ttl=117 time=12.689 ms
64 bytes from 172.217.13.164: icmp_seq=227 ttl=117 time=12.074 ms
Traceroute has started…
traceroute to www.google.com (172.217.13.196), 64 hops max, 72 byte packets
1 10.0.0.1 (10.0.0.1) 4.402 ms 3.265 ms 4.244 ms
2 cpe18593394b320-cm18593394b31d.cpe.net.cable.rogers.com (173.35.38.75) 1216.602 ms !H
173.32.44.1 (173.32.44.1) 7.740 ms 5.037 ms
3 209.148.231.205 (209.148.231.205) 12.123 ms 6.204 ms 8.234 ms
4 209.148.238.254 (209.148.238.254) 5.681 ms 5.576 ms 9.528 ms
5 209.148.233.130 (209.148.233.130) 9.258 ms 10.637 ms 9.258 ms
6 * * *
7 * * *
8 * * 108.170.231.65 (108.170.231.65) 11.402 ms
9 yul03s05-in-f4.1e100.net (172.217.13.196) 10.075 ms 10.067 ms 8.147 ms
Hoping for some solutions to my problem!
11-15-2022 01:45 PM
Greetings @522606!
That looks like a heavy amount of packet loss. I'd like to take a closer look here and run some tests.
Feel free to send a private message to @CommunityHelps so we can assist you further. For more information on how our Private Messaging system works, you can find out more here.
Regards,
RogersCorey