Packet loss and ping spikes
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
02-18-2023
11:14 AM
- last edited on
02-18-2023
04:05 PM
by
RogersTony
I've been having issues for the couple months where my internet would randomly drop out or become slow for about 10 minutes. I notice this most when doing video calls or playing games. It would happen randomly throughout the day so its been hard figuring out the issue. I've had 3 rogers tech come in and they've all tried to change something(bad cable to the house, replaced a connection inside my house, replaced a modem) but it hasn't fixed the issue.
I restarted my modem and the issue was still happening. So I captured some ping and traceroute information.
Anyone know what the problem might be?
ping -n 100 8.8.8.8
Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 59, Lost = 41 (41% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 3665ms, Average = 381ms
tracert 8.8.8.8
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 10.0.0.1
2 * * 728 ms 99.243.182.1
3 505 ms 1119 ms 1115 ms 8076-dgw01.lndn.rmgt.net.rogers.com [67.231.221.125]
4 1781 ms 692 ms 190 ms 69.63.250.129
5 19 ms 40 ms 214 ms 209.148.235.222
6 71 ms 65 ms 61 ms 72.14.216.54
7 577 ms 87 ms 347 ms 209.85.249.37
8 447 ms 317 ms * 216.239.40.255
9 97 ms * * dns.google [8.8.8.8]
10 3964 ms * * dns.google [8.8.8.8]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * 926 ms dns.google [8.8.8.8]
traceroute from the modem's webpage directly
Status: Complete !
1: *
2: 247,23,86 8076-dgw01.lndn.rmgt.net.rogers.com 67.231.221.125
3: 136,11 69.63.250.129 69.63.250.129
4: 98,103,66 209.148.235.222 209.148.235.222
5: 40 72.14.216.54 72.14.216.54
6: *
7: 20,52,53 172.253.69.113 172.253.69.113
8: 22,37,37 dns.google 8.8.8.8
ping -n 60 10.0.0.1
Ping statistics for 10.0.0.1:
Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms
ping -n 60 99.243.182.1 (first hop, this was done last and internet was sort of recovering)
Ping statistics for 99.243.182.1:
Packets: Sent = 60, Received = 56, Lost = 4 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 521ms, Average = 55ms
Modem stats
IndexLock StatusFrequencySNRPower LevelModulation
Downstream
|
Channel Bonding Value | |||||||||||||||||||||||||||||||||
20
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
34
|
33
|
34
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
693 MHz
|
279 MHz
|
579 MHz
|
585 MHz
|
591 MHz
|
597 MHz
|
603 MHz
|
609 MHz
|
615 MHz
|
621 MHz
|
633 MHz
|
639 MHz
|
645 MHz
|
651 MHz
|
657 MHz
|
663 MHz
|
669 MHz
|
675 MHz
|
681 MHz
|
687 MHz
|
699 MHz
|
705 MHz
|
711 MHz
|
717 MHz
|
723 MHz
|
825 MHz
|
831 MHz
|
837 MHz
|
843 MHz
|
849 MHz
|
855 MHz
|
861 MHz
|
216 MHz
|
350000000
|
216000000
|
43.6 dB
|
40.0 dB
|
42.9 dB
|
43.0 dB
|
42.8 dB
|
43.0 dB
|
42.8 dB
|
43.0 dB
|
43.0 dB
|
43.1 dB
|
43.5 dB
|
43.1 dB
|
43.3 dB
|
43.1 dB
|
43.1 dB
|
43.3 dB
|
43.1 dB
|
42.5 dB
|
43.5 dB
|
43.4 dB
|
43.6 dB
|
43.6 dB
|
43.7 dB
|
43.3 dB
|
43.1 dB
|
43.2 dB
|
43.1 dB
|
43.3 dB
|
43.1 dB
|
42.5 dB
|
43.1 dB
|
43.0 dB
|
40.7 dB
|
41.8 dB
|
40.7 dB
|
5.8 dBmV
|
-1.8 dBmV
|
3.3 dBmV
|
3.1 dBmV
|
3.1 dBmV
|
3.4 dBmV
|
3.0 dBmV
|
3.6 dBmV
|
4.0 dBmV
|
3.6 dBmV
|
5.0 dBmV
|
4.5 dBmV
|
4.9 dBmV
|
4.7 dBmV
|
4.4 dBmV
|
5.4 dBmV
|
4.9 dBmV
|
5.1 dBmV
|
6.3 dBmV
|
6.2 dBmV
|
6.7 dBmV
|
6.4 dBmV
|
7.1 dBmV
|
6.9 dBmV
|
6.0 dBmV
|
6.6 dBmV
|
6.7 dBmV
|
7.5 dBmV
|
6.4 dBmV
|
5.1 dBmV
|
6.4 dBmV
|
6.4 dBmV
|
0.2 dBmV
|
0.7 dBmV
|
0.2 dBmV
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
OFDM
|
OFDM
|
OFDM
|
IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type
Upstream
|
Channel Bonding Value | |||
1
|
2
|
3
|
4
|
5
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
21 MHz
|
25 MHz
|
32 MHz
|
38 MHz
|
4 MHz
|
2560
|
5120
|
5120
|
5120
|
0
|
38.0 dBmV
|
40.0 dBmV
|
40.8 dBmV
|
41.3 dBmV
|
38.0 dBmV
|
QAM
|
QAM
|
QAM
|
QAM
|
OFDMA
|
TDMA_AND_ATDMA
|
ATDMA
|
ATDMA
|
ATDMA
|
TDMA
|
IndexUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
CM Error Codewords | |||||||||||||||||||||||||||||||||
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
33
|
34
|
8248151
|
49955487
|
49963200
|
49967942
|
49972055
|
49977311
|
49982576
|
49987581
|
49992525
|
49997367
|
50002276
|
50007332
|
50012596
|
50016910
|
50022807
|
50027455
|
50032869
|
50038092
|
50042366
|
50048234
|
50052869
|
50058476
|
50063222
|
50068302
|
50072822
|
50077966
|
50082656
|
50087266
|
50092656
|
50097914
|
50097868
|
50100232
|
9428148
|
8248151
|
5408465
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
8999992
|
5408465
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
- Labels:
-
Internet
-
Latency
-
Troubleshooting
Re: Packet loss and ping spikes
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
02-19-2023 10:52 AM
Greetings @teriscod!
That's an awful lot of packet loss to be remaining after we've had 3 techs come out. There must be something else going on here.
We'd be happy to take a closer look to see what is going on! 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

