12-05-2022 00:23 - edited 12-05-2022 01:11
New GIG1 install, the lines only got built into this area of the country a few weeks ago and I have been wired up for about 2 weeks or so.
So I had been noticing some weird issues where a youtube or twitch stream would buffer or cut out for a few seconds (something that should never happen on a gig connection). I also then played a game on the switch and had some lag spikes, another thing I never thought I would see again after moving from my old 30mb BT broadband connection.
But most of the time when I did an ookla speed test, it would be perfectly fine 14ms-16ms 900+Mbps. But occasionally (very rarely) it would instead throw out a ~350Mbps result... but another test would go back to normal. So at first I just thought the bad test happened cos something else was using the bandwidth at that time.
So I hunted out a test that actually did consistent automatic reporting, and came across this:
This picture is pretty consistent with what I would see. Mostly fine, but occasional very high spikes. I then set up my server to run 24 hours of consistent speed tests just to see if there were any trends. These tests were run every couple of minutes.
So I kept looking for a better test that may actually give me some info on what's wrong, and popped into this forum and saw the ThinkBroadband one that was being used, and immediately signed up, expecting to have to wait a couple days to get any kind of picture of what might be going on. I'll post up the link in here once I have it up and running properly, but as there does seem to be something very wrong with the speed consistency I thought I'd post up and see if anyone had any immediate advice for me to get started with!
on 12-05-2022 00:35
Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream
Cable Modem Status | Online | DOCSIS 3.1 |
Primary downstream channel | Locked | SC-QAM |
DOCSIS 3.0 channels | 31 | 4 |
DOCSIS 3.1 channels | 1 | 0 |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | 5.000000 | 37.636276 | QAM256 | 25 |
1 | 139000000 | 6.599998 | 36.386890 | QAM256 | 1 |
2 | 147000000 | 6.599998 | 36.386890 | QAM256 | 2 |
3 | 155000000 | 6.599998 | 36.609653 | QAM256 | 3 |
4 | 163000000 | 6.699997 | 36.609653 | QAM256 | 4 |
5 | 171000000 | 6.599998 | 36.609653 | QAM256 | 5 |
6 | 179000000 | 6.699997 | 36.609653 | QAM256 | 6 |
7 | 187000000 | 6.900002 | 37.636276 | QAM256 | 7 |
8 | 195000000 | 6.800003 | 37.355988 | QAM256 | 8 |
9 | 203000000 | 6.900002 | 37.355988 | QAM256 | 9 |
10 | 211000000 | 6.900002 | 37.636276 | QAM256 | 10 |
11 | 219000000 | 6.900002 | 37.636276 | QAM256 | 11 |
12 | 227000000 | 6.900002 | 36.609653 | QAM256 | 12 |
13 | 235000000 | 6.800003 | 37.636276 | QAM256 | 13 |
14 | 243000000 | 6.800003 | 37.636276 | QAM256 | 14 |
15 | 251000000 | 6.699997 | 37.355988 | QAM256 | 15 |
16 | 259000000 | 6.500000 | 36.609653 | QAM256 | 16 |
17 | 267000000 | 6.199997 | 37.355988 | QAM256 | 17 |
18 | 275000000 | 5.699997 | 37.355988 | QAM256 | 18 |
19 | 283000000 | 5.400002 | 37.355988 | QAM256 | 19 |
20 | 291000000 | 5.300003 | 37.636276 | QAM256 | 20 |
21 | 299000000 | 5.599998 | 37.636276 | QAM256 | 21 |
22 | 307000000 | 5.599998 | 37.636276 | QAM256 | 22 |
23 | 315000000 | 5.400002 | 37.355988 | QAM256 | 23 |
24 | 323000000 | 5.000000 | 36.609653 | QAM256 | 24 |
26 | 339000000 | 5.099998 | 37.636276 | QAM256 | 26 |
27 | 347000000 | 5.099998 | 37.355988 | QAM256 | 27 |
28 | 355000000 | 5.099998 | 37.636276 | QAM256 | 28 |
29 | 363000000 | 5.099998 | 37.355988 | QAM256 | 29 |
30 | 371000000 | 5.199997 | 37.636276 | QAM256 | 30 |
31 | 379000000 | 5.300003 | 37.355988 | QAM256 | 31 |
on 12-05-2022 00:35
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 37.636276 | 0 | 0 |
1 | Locked | 36.386890 | 0 | 0 |
2 | Locked | 36.386890 | 1 | 0 |
3 | Locked | 36.609653 | 0 | 0 |
4 | Locked | 36.609653 | 0 | 0 |
5 | Locked | 36.609653 | 0 | 0 |
6 | Locked | 36.609653 | 0 | 0 |
7 | Locked | 37.636276 | 0 | 0 |
8 | Locked | 37.355988 | 0 | 0 |
9 | Locked | 37.355988 | 0 | 0 |
10 | Locked | 37.636276 | 0 | 0 |
11 | Locked | 37.636276 | 0 | 0 |
12 | Locked | 36.609653 | 0 | 0 |
13 | Locked | 37.636276 | 0 | 0 |
14 | Locked | 37.636276 | 0 | 0 |
15 | Locked | 37.355988 | 0 | 0 |
16 | Locked | 36.609653 | 0 | 0 |
17 | Locked | 37.355988 | 0 | 0 |
18 | Locked | 37.355988 | 0 | 0 |
19 | Locked | 37.355988 | 0 | 0 |
20 | Locked | 37.636276 | 0 | 0 |
21 | Locked | 37.636276 | 0 | 0 |
22 | Locked | 37.636276 | 0 | 0 |
23 | Locked | 37.355988 | 0 | 0 |
24 | Locked | 36.609653 | 0 | 0 |
26 | Locked | 37.636276 | 0 | 0 |
27 | Locked | 37.355988 | 0 | 0 |
28 | Locked | 37.636276 | 0 | 0 |
29 | Locked | 37.355988 | 0 | 0 |
30 | Locked | 37.636276 | 0 | 0 |
31 | Locked | 37.355988 | 0 | 0 |
33 | 96 | 4K | 1880 | QAM4096 | 759 |
33 | Locked | 40 | 7.3 | 826304526 | 0 |
12-05-2022 00:43 - edited 12-05-2022 01:12
Deleted - put it into the first post instead.
on 12-05-2022 02:08
https://www.thinkbroadband.com/broadband/monitoring/quality/share/bcde296e62891cbe2da856eec0c213052869cf24
My thinkbroadband live link. Though currently isn't showing anything obvious (to my eyes) but then it also doesn't seem to deal with speed at all so I dunno if it's relevant to my issue...
on 14-05-2022 11:45
Hi nirurin,
Thank you for reaching back out, sorry to see you are still seeing latency spikes and a lower connection than expected, I have had a look at things your end and cannot see any issues other than possible WIFI issues, how are you running the speed test, wired or WIFI?
regards
Paul.
15-05-2022 00:37 - edited 15-05-2022 00:44
Are you in modem mode for the hub?
Your line is shared so bandwidth can drop or routing is overloaded somewhere to send 1Gb to you.
on 15-05-2022 07:49
Nothing here is set up using wifi. Server and PC are both hard wired.
on 15-05-2022 21:09
on 18-05-2022 09:17
Good Morning @niruin, thanks for coming back to us
I've been able to run through a flow and it appears that, our system has identified a short-term connectivity issue which may cause intermittent or performance related issues, and n the vast majority of cases, these types of issues are resolved after 24 hours.
The system hasn’t identified any other issues that would impact the connection and we believe it will only be a short-term issue and the connection will return to normal after 24 hours.
Our network can sometimes be susceptible to the occasional blip. These can be caused be network fixes happening in the area or new customers being installed
Kindest regards,
David_Bn