Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Ignite 1.5 Gb service: Horrible latency spikes on evenings and weekends

fdskjfklasjfask
I'm here a lot

‎02-15-2024 10:16 AM - edited ‎02-15-2024 10:38 AM

Hi,

 

I'll start with my configuration, then I'll detail my issue:

 

Service:  1.5 Gb

Modem:  Technicolor CGM4981COM   revision 2.0

Connection:  Bridged; all machines connected via Ethernet, and the test machine I've been using to collect statistics is directly connected to the 2.5 Gb port (although I did run the below tests for a couple of days routed, via direct Ethernet connection to the 2.5 Gb port on the modem, and the results were identical)

 

Signal levels:

 

Channel IDLock StatusFrequencySNRPower LevelModulation

Downstream
Channel Bonding Value
23
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
24
25
26
27
28
29
30
31
32
33
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
849 MHz
855 MHz
861 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
350000000
45.2 dB
45.3 dB
45.9 dB
45.9 dB
45.7 dB
45.2 dB
45.6 dB
45.6 dB
45.5 dB
45.6 dB
45.5 dB
44.7 dB
45.9 dB
45.8 dB
45.7 dB
45.8 dB
45.7 dB
45.7 dB
45.5 dB
45.3 dB
43.9 dB
45.0 dB
44.9 dB
45.4 dB
45.6 dB
45.6 dB
45.4 dB
45.3 dB
45.8 dB
45.7 dB
45.8 dB
45.9 dB
45.4 dB
3.8 dBmV
2.1 dBmV
6.3 dBmV
6.0 dBmV
5.3 dBmV
3.7 dBmV
4.3 dBmV
4.3 dBmV
4.4 dBmV
4.5 dBmV
4.4 dBmV
4.3 dBmV
4.7 dBmV
4.7 dBmV
4.7 dBmV
4.8 dBmV
4.8 dBmV
4.7 dBmV
4.4 dBmV
4.3 dBmV
3.9 dBmV
3.7 dBmV
3.7 dBmV
4.2 dBmV
4.5 dBmV
4.6 dBmV
4.4 dBmV
4.2 dBmV
5.7 dBmV
6.0 dBmV
6.0 dBmV
6.4 dBmV
3.4 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
 

 

Channel IDLock StatusFrequencySymbol RatePower LevelModulationChannel Type

Upstream
Channel Bonding Value
1
2
3
4
Locked
Locked
Locked
Locked
21 MHz
25 MHz
32 MHz
38 MHz
2560
5120
5120
5120
37.5 dBmV
41.3 dBmV
41.8 dBmV
41.5 dBmV
QAM
QAM
QAM
QAM
TDMA_AND_ATDMA
ATDMA
ATDMA
ATDMA

 

Channel IDUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords

CM Error Codewords
23
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
24
25
26
27
28
29
30
31
32
33
2014843450
2111575153
2111570268
2111594973
2111614019
2111624071
2111634551
2111652599
2111648740
2111658287
2111759137
2111774054
2111768142
2111774311
2111780664
2111721448
2171406036
2171408707
2171459489
2171463326
2171510866
2171520837
2171528224
2171533662
2171527734
2171537403
2171546025
2171543539
2171521282
2171519680
2171494554
2171494697
2014843450
3538967762
1101
331
339
299
515
525
419
488
419
437
351
369
400
338
361
325
383
440
377
526
294
411
327
313
321
273
366
328
305
254
311
3538967762
95707
2588
1050
1091
1110
1191
1328
1139
1426
1081
1366
1141
1169
1163
1134
620
649
1039
1217
1022
1239
1031
1160
1099
1027
1118
1038
1050
1021
1134
1031
1069
95707

 

How long have I had this issue:  Since I first activated the service, early January of this year

How often:  Almost every evening and several hours on weekends; some days are much worse than others

 

The Problem

 

Bad latency spikes (ping times > 100 ms) lasting anywhere from a few seconds to a minute or two at a time.  This makes the service completely unusable for gaming, VOIP calling, or videoconferencing (ie. MS Teams, Zoom), especially since most evenings I need to do a fair amount of videoconferencing for my job.

 

I've been using SmokePing to graph the problem, along with a "one ping per second" that's been running on the directly-Ethernet-connected computer (and yes, I have tried more than one computer, running each of Linux, MacOS, and Windows 10).

 

Normal:
 
normal.jpg
 
Please note, even during the day, I don't always get constant "within reasonable limits" pings; for example, that grey spike between 10:05 and 10:10; that corresponds to this ping sequence (> 60 ms at 10:05:23):
 

 

2024-02-15T10:05:22 64 bytes from 99.235.96.1: icmp_seq=13325 ttl=63 time=10.055 ms
2024-02-15T10:05:23 64 bytes from 99.235.96.1: icmp_seq=13326 ttl=63 time=61.823 ms
2024-02-15T10:05:24 64 bytes from 99.235.96.1: icmp_seq=13327 ttl=63 time=18.126 ms

 

However, as bad as those are, they don't come anywhere near what I get in the evenings and weekends.  Here's yesterday evening:
 
571A528D-35A7-469E-A08D-93C5E224B554_1_102_o.jpeg5E274D83-3F39-4080-BDDF-BDB3E551D386_1_102_o.jpegD2EAF5F0-1D39-4177-BFBD-68C210FC9E5F_1_102_o.jpeg
 
Notice the huge spikes, especially between 20:40 and 20:45.  The pings during that timeframe:
 

 

2024-02-14T20:40:38 64 bytes from 99.235.96.1: icmp_seq=31006 ttl=63 time=28.391 ms
2024-02-14T20:40:39 64 bytes from 99.235.96.1: icmp_seq=31007 ttl=63 time=39.884 ms
2024-02-14T20:40:40 64 bytes from 99.235.96.1: icmp_seq=31008 ttl=63 time=306.331 ms
2024-02-14T20:40:41 64 bytes from 99.235.96.1: icmp_seq=31009 ttl=63 time=39.976 ms
2024-02-14T20:40:42 64 bytes from 99.235.96.1: icmp_seq=31010 ttl=63 time=14.648 ms
2024-02-14T20:40:43 64 bytes from 99.235.96.1: icmp_seq=31011 ttl=63 time=23.669 ms
2024-02-14T20:40:44 64 bytes from 99.235.96.1: icmp_seq=31012 ttl=63 time=12.803 ms
2024-02-14T20:40:45 64 bytes from 99.235.96.1: icmp_seq=31013 ttl=63 time=15.411 ms
2024-02-14T20:40:46 64 bytes from 99.235.96.1: icmp_seq=31014 ttl=63 time=17.385 ms
2024-02-14T20:40:47 64 bytes from 99.235.96.1: icmp_seq=31015 ttl=63 time=17.347 ms
2024-02-14T20:40:48 64 bytes from 99.235.96.1: icmp_seq=31016 ttl=63 time=16.929 ms
2024-02-14T20:40:49 64 bytes from 99.235.96.1: icmp_seq=31017 ttl=63 time=19.947 ms
2024-02-14T20:40:50 64 bytes from 99.235.96.1: icmp_seq=31018 ttl=63 time=26.250 ms
2024-02-14T20:40:51 64 bytes from 99.235.96.1: icmp_seq=31019 ttl=63 time=23.268 ms
2024-02-14T20:40:52 64 bytes from 99.235.96.1: icmp_seq=31020 ttl=63 time=22.098 ms
2024-02-14T20:40:53 64 bytes from 99.235.96.1: icmp_seq=31021 ttl=63 time=13.783 ms
2024-02-14T20:40:54 64 bytes from 99.235.96.1: icmp_seq=31022 ttl=63 time=23.906 ms
2024-02-14T20:40:55 64 bytes from 99.235.96.1: icmp_seq=31023 ttl=63 time=160.946 ms
2024-02-14T20:40:56 64 bytes from 99.235.96.1: icmp_seq=31024 ttl=63 time=131.283 ms
2024-02-14T20:40:58 64 bytes from 99.235.96.1: icmp_seq=31025 ttl=63 time=743.380 ms
2024-02-14T20:40:58 64 bytes from 99.235.96.1: icmp_seq=31026 ttl=63 time=16.363 ms
2024-02-14T20:41:00 64 bytes from 99.235.96.1: icmp_seq=31027 ttl=63 time=748.976 ms
2024-02-14T20:41:00 64 bytes from 99.235.96.1: icmp_seq=31028 ttl=63 time=59.302 ms
2024-02-14T20:41:02 64 bytes from 99.235.96.1: icmp_seq=31029 ttl=63 time=580.521 ms
2024-02-14T20:41:03 64 bytes from 99.235.96.1: icmp_seq=31030 ttl=63 time=786.917 ms
2024-02-14T20:41:03 64 bytes from 99.235.96.1: icmp_seq=31031 ttl=63 time=52.965 ms
2024-02-14T20:41:04 64 bytes from 99.235.96.1: icmp_seq=31032 ttl=63 time=33.790 ms
2024-02-14T20:41:05 64 bytes from 99.235.96.1: icmp_seq=31033 ttl=63 time=220.553 ms
2024-02-14T20:41:06 64 bytes from 99.235.96.1: icmp_seq=31034 ttl=63 time=28.680 ms
2024-02-14T20:41:07 64 bytes from 99.235.96.1: icmp_seq=31035 ttl=63 time=43.982 ms
2024-02-14T20:41:08 64 bytes from 99.235.96.1: icmp_seq=31036 ttl=63 time=25.968 ms
2024-02-14T20:41:09 64 bytes from 99.235.96.1: icmp_seq=31037 ttl=63 time=63.869 ms
2024-02-14T20:41:10 64 bytes from 99.235.96.1: icmp_seq=31038 ttl=63 time=17.315 ms
2024-02-14T20:41:11 64 bytes from 99.235.96.1: icmp_seq=31039 ttl=63 time=56.719 ms
2024-02-14T20:41:12 64 bytes from 99.235.96.1: icmp_seq=31040 ttl=63 time=18.424 ms
2024-02-14T20:41:13 64 bytes from 99.235.96.1: icmp_seq=31041 ttl=63 time=32.813 ms
2024-02-14T20:41:14 64 bytes from 99.235.96.1: icmp_seq=31042 ttl=63 time=10.520 ms
2024-02-14T20:41:15 64 bytes from 99.235.96.1: icmp_seq=31043 ttl=63 time=19.245 ms
2024-02-14T20:41:16 64 bytes from 99.235.96.1: icmp_seq=31044 ttl=63 time=17.377 ms
2024-02-14T20:41:17 64 bytes from 99.235.96.1: icmp_seq=31045 ttl=63 time=15.981 ms
2024-02-14T20:41:18 64 bytes from 99.235.96.1: icmp_seq=31046 ttl=63 time=15.700 ms
2024-02-14T20:41:19 64 bytes from 99.235.96.1: icmp_seq=31047 ttl=63 time=16.178 ms
2024-02-14T20:41:20 64 bytes from 99.235.96.1: icmp_seq=31048 ttl=63 time=18.128 ms
2024-02-14T20:41:21 64 bytes from 99.235.96.1: icmp_seq=31049 ttl=63 time=10.800 ms
2024-02-14T20:41:22 64 bytes from 99.235.96.1: icmp_seq=31050 ttl=63 time=16.231 ms
2024-02-14T20:41:23 64 bytes from 99.235.96.1: icmp_seq=31051 ttl=63 time=19.425 ms
2024-02-14T20:41:24 64 bytes from 99.235.96.1: icmp_seq=31052 ttl=63 time=12.683 ms
2024-02-14T20:41:25 64 bytes from 99.235.96.1: icmp_seq=31053 ttl=63 time=12.033 ms
2024-02-14T20:41:26 64 bytes from 99.235.96.1: icmp_seq=31054 ttl=63 time=108.991 ms
2024-02-14T20:41:27 64 bytes from 99.235.96.1: icmp_seq=31055 ttl=63 time=15.335 ms
2024-02-14T20:41:28 64 bytes from 99.235.96.1: icmp_seq=31056 ttl=63 time=11.938 ms
2024-02-14T20:41:29 64 bytes from 99.235.96.1: icmp_seq=31057 ttl=63 time=14.803 ms
2024-02-14T20:41:31 64 bytes from 99.235.96.1: icmp_seq=31058 ttl=63 time=355.431 ms
2024-02-14T20:41:31 64 bytes from 99.235.96.1: icmp_seq=31059 ttl=63 time=87.608 ms
2024-02-14T20:41:32 64 bytes from 99.235.96.1: icmp_seq=31060 ttl=63 time=41.129 ms
2024-02-14T20:41:34 64 bytes from 99.235.96.1: icmp_seq=31061 ttl=63 time=253.713 ms
2024-02-14T20:41:35 64 bytes from 99.235.96.1: icmp_seq=31062 ttl=63 time=468.533 ms
2024-02-14T20:41:35 64 bytes from 99.235.96.1: icmp_seq=31063 ttl=63 time=19.316 ms
2024-02-14T20:41:36 64 bytes from 99.235.96.1: icmp_seq=31064 ttl=63 time=33.844 ms
2024-02-14T20:41:38 64 bytes from 99.235.96.1: icmp_seq=31065 ttl=63 time=533.238 ms
2024-02-14T20:41:38 64 bytes from 99.235.96.1: icmp_seq=31066 ttl=63 time=53.992 ms
2024-02-14T20:41:39 64 bytes from 99.235.96.1: icmp_seq=31067 ttl=63 time=89.571 ms
2024-02-14T20:41:41 64 bytes from 99.235.96.1: icmp_seq=31068 ttl=63 time=139.388 ms
2024-02-14T20:41:42 64 bytes from 99.235.96.1: icmp_seq=31069 ttl=63 time=226.439 ms
2024-02-14T20:41:43 64 bytes from 99.235.96.1: icmp_seq=31070 ttl=63 time=143.152 ms
2024-02-14T20:41:44 64 bytes from 99.235.96.1: icmp_seq=31071 ttl=63 time=120.152 ms
2024-02-14T20:41:45 64 bytes from 99.235.96.1: icmp_seq=31072 ttl=63 time=604.133 ms
2024-02-14T20:41:46 64 bytes from 99.235.96.1: icmp_seq=31073 ttl=63 time=82.514 ms
2024-02-14T20:41:46 64 bytes from 99.235.96.1: icmp_seq=31074 ttl=63 time=16.615 ms
2024-02-14T20:41:48 64 bytes from 99.235.96.1: icmp_seq=31075 ttl=63 time=267.282 ms
2024-02-14T20:41:49 64 bytes from 99.235.96.1: icmp_seq=31076 ttl=63 time=943.188 ms
2024-02-14T20:41:50 64 bytes from 99.235.96.1: icmp_seq=31077 ttl=63 time=172.552 ms
2024-02-14T20:41:51 64 bytes from 99.235.96.1: icmp_seq=31078 ttl=63 time=1000.852 ms
2024-02-14T20:41:52 64 bytes from 99.235.96.1: icmp_seq=31079 ttl=63 time=69.436 ms
2024-02-14T20:41:53 64 bytes from 99.235.96.1: icmp_seq=31080 ttl=63 time=169.939 ms
2024-02-14T20:41:54 64 bytes from 99.235.96.1: icmp_seq=31081 ttl=63 time=241.596 ms
2024-02-14T20:41:55 64 bytes from 99.235.96.1: icmp_seq=31082 ttl=63 time=195.665 ms
2024-02-14T20:41:56 64 bytes from 99.235.96.1: icmp_seq=31083 ttl=63 time=200.956 ms
2024-02-14T20:41:57 64 bytes from 99.235.96.1: icmp_seq=31084 ttl=63 time=576.591 ms
2024-02-14T20:41:57 64 bytes from 99.235.96.1: icmp_seq=31085 ttl=63 time=15.949 ms
2024-02-14T20:41:58 64 bytes from 99.235.96.1: icmp_seq=31086 ttl=63 time=27.318 ms
2024-02-14T20:42:01 64 bytes from 99.235.96.1: icmp_seq=31087 ttl=63 time=1137.434 ms
2024-02-14T20:42:01 64 bytes from 99.235.96.1: icmp_seq=31088 ttl=63 time=135.548 ms

 

 
I won't include any more data here, as they don't really say anything different from the above.
 
At any rate, as per my post from a few days ago, I have tried the normal stuff (reboot computers; unplug power to modem for 30+ seconds before plugging back in; check all coax connections to ensure they're "snug"; etc.).
Labels:
0 Likes
3 REPLIES 3

Re: Ignite 1.5 Gb service: Horrible latency spikes on evenings and weekends

james039
I plan to stick around

‎02-15-2024 10:46 AM

The pattern you are describing is very typical for heavy usage periods on cable internet networks. It's been the case on cable for decades that during hours of high demand the connection will throttle due to the demand the users are placing on the network. I think it's worthwhile to talk about this, since it could be somewhat mitigated using more clever QoS during these times, but it's likely there is nothing wrong with your specific connection. Everyone experiences this.

0 Likes

Re: Ignite 1.5 Gb service: Horrible latency spikes on evenings and weekends

fdskjfklasjfask
I'm here a lot
In response to james039

‎02-15-2024 10:55 AM - edited ‎02-15-2024 12:32 PM

Funny you should mention this; outside of the times when I've run diagnostics tests, I actually do make heavy use of QoS (CoDEL primarily, using a configuring I've tweaked quite frequently over the years), because it's the only way I can pass bufferbloat tests (restricting my speeds to 400/30 gives me frequent "A+"'s on the Waveform.com bufferbloat tester).

 

And yes, you read that right:  400 down.  Even in the middle of the day, I get bufferbloat if I set it to a higher speed.  And if I set the limit to, say, 1 Gb down or completely remove the shaping, I get a "D".  😱

 

Edit:  I should add:  QoS won't do anything for this issue - when I run the tests, I'm downloading well under 5 Mb/s data, and uploading under 1 Mb/s - the only way QoS would work is if it were done at the CMTS (in theory).

0 Likes

Re: Ignite 1.5 Gb service: Horrible latency spikes on evenings and weekends

RogersYasmine
Moderator
Moderator
In response to fdskjfklasjfask

‎02-17-2024 11:29 AM

Hello @fdskjfklasjfask ,

 

Welcome to the community and thanks for the detailed post! 🙂

 

We definitely want to ensure you are getting the most out of your internet services with us. I'm sorry to hear that you've been experiencing these latency issues since activating your services with us, that's not ideal.

 

If possible, please send us a PM @CommunityHelps, the next time you are online, and we'll be happy to do some checks and troubleshoot with you further. For more information on how our Private Messaging system works, please check out our blog.
 

 

Thank you!

RogersYasmine

 

 

0 Likes
Topic Stats
  • 3 replies
  • ‎02-15-2024 10:16 AM
  • 1239 views
  • 0 Likes
  • 3 in conversation
Copyright © 2024 Khoros, LLC