13-10-2021 21:12 - edited 13-10-2021 21:18
Hi again, I'll have to split the post into various parts due to character limits.
So for a while my connection has been "Less than ideal". (My previous posts reflected this)
However the last week or more it has been worse than usual, ping spikes while having videos playing in the background (even just 1080p music videos)
In fact the spikes are worse than the TBB Graph shows.
Then early this morning(Just after 11AM) I had a full outage (Partial service in logs, which I will post further down), as well as QAM dropping.
Even prior to today, the T3 timeouts that would also occur happened in bursts on each upstream channel. - luckily not
Bit of info:
HP2 Area,
Super hub 3,
Modem mode(although this shouldn't matter, right?)
Graph from today (13th october):
https://www.thinkbroadband.com/broadband/monitoring/quality/share/942d91a395a26f3dd31266c72a6884cb61a6350d-13-10-2021
Live Graph:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/3f9a0c6eff35d57ae0f42e221bb1b8b92039be2d
The larger average latency spikes are from speed tests/people updating stuff on their phones.
I can provide graphs from further back if needed.
On to the logs:
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz) | 699000000 | Locked |
Ranged Upstream Channel (Hz) | 46200000 | Locked |
Provisioning State | Online |
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 699000000 | 4.5 | 40 | 256 qam | 37 |
2 | 539000000 | 4.5 | 38 | 256 qam | 17 |
3 | 547000000 | 4.9 | 40 | 256 qam | 18 |
4 | 555000000 | 5 | 40 | 256 qam | 19 |
5 | 563000000 | 4.5 | 38 | 256 qam | 20 |
6 | 571000000 | 3.7 | 38 | 256 qam | 21 |
7 | 579000000 | 3.2 | 38 | 256 qam | 22 |
8 | 587000000 | 3.5 | 38 | 256 qam | 23 |
9 | 595000000 | 4 | 38 | 256 qam | 24 |
10 | 603000000 | 4.5 | 38 | 256 qam | 25 |
11 | 611000000 | 4.4 | 40 | 256 qam | 26 |
12 | 619000000 | 4 | 38 | 256 qam | 27 |
13 | 627000000 | 3.7 | 38 | 256 qam | 28 |
14 | 635000000 | 4 | 38 | 256 qam | 29 |
15 | 643000000 | 4.3 | 38 | 256 qam | 30 |
16 | 651000000 | 4.6 | 38 | 256 qam | 31 |
17 | 659000000 | 4.4 | 38 | 256 qam | 32 |
18 | 667000000 | 4.1 | 38 | 256 qam | 33 |
19 | 675000000 | 4 | 38 | 256 qam | 34 |
20 | 683000000 | 4 | 38 | 256 qam | 35 |
21 | 691000000 | 4.5 | 38 | 256 qam | 36 |
22 | 707000000 | 4.3 | 38 | 256 qam | 38 |
23 | 715000000 | 3.7 | 38 | 256 qam | 39 |
24 | 723000000 | 3.4 | 38 | 256 qam | 40 |
I should also note: the power levels before the outage were in the 7 ~ 7.5 range. - unsure if this is of any relevance since they're still in range.
More so just wondering if it's part of the problem.
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 20789 | 1490 |
2 | Locked | 38.9 | 12227 | 1519 |
3 | Locked | 40.3 | 13374 | 1571 |
4 | Locked | 40.3 | 13192 | 1642 |
5 | Locked | 38.9 | 14011 | 1637 |
6 | Locked | 38.9 | 16810 | 1531 |
7 | Locked | 38.9 | 20184 | 2512 |
8 | Locked | 38.6 | 21187 | 2611 |
9 | Locked | 38.6 | 20780 | 1768 |
10 | Locked | 38.9 | 20562 | 1933 |
11 | Locked | 40.3 | 19913 | 2445 |
12 | Locked | 38.9 | 21657 | 3878 |
13 | Locked | 38.6 | 23632 | 3311 |
14 | Locked | 38.6 | 24594 | 1900 |
15 | Locked | 38.6 | 23876 | 2238 |
16 | Locked | 38.9 | 22765 | 2252 |
17 | Locked | 38.6 | 22882 | 1623 |
18 | Locked | 38.9 | 23041 | 4006 |
19 | Locked | 38.9 | 22662 | 3496 |
20 | Locked | 38.6 | 23448 | 2519 |
21 | Locked | 38.9 | 22031 | 2614 |
22 | Locked | 38.6 | 20555 | 2865 |
23 | Locked | 38.6 | 21454 | 2039 |
24 | Locked | 38.9 | 20845 | 3970 |
These post RS haven't raised any higher since the outage happened earlier today.
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 39 | 5120 | 64 qam | 1 |
2 | 39400000 | 38.8 | 5120 | 64 qam | 2 |
3 | 32600000 | 38.5 | 5120 | 16 qam | 3 |
4 | 25800088 | 37.8 | 5120 | 64 qam | 4 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 6 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 19-12-2021 14:38
Thanks for getting back to us @Icantcrabhere.
I've taken a look into things for you, and I can see there is an issue in the area currently.
This is causing intermittent service and is due to be resolved 20/12/21 at 13:55.
If you find the issues persist once this has been resolved, please let us know.
Thanks,
New around here? To find out more about the Community check out our Getting Started guide
on 19-12-2021 15:21
Hi Sofia!
Is there any chance you have a reference number?
Also is there description of the fault, or is it needing to be investigated?
Thank you for the update, however!
Much appreciated
on 21-12-2021 15:59
Hi @Icantcrabhere, thanks for your post.
I've checked your account and the should now be resolved for you, it seemed to have been fixed at the same time Hayley mentioned it should've been.
Can you please confirm if you're still having issues?
As Sofia's post said, it was being investigated which is why she could locate the outage on your account - thankfully this now appear to be fixed!
Please let me know if you still need further assistance.
Regards
on 21-12-2021 16:28
Hi tom!
It does indeed seem to be fixed, I'll be keeping an eye on it to be sure however!
I'm wondering if you could tell me what the cause of the issue actually was?
My interest is peaked, since it plagued me for a while.
Thanks again for the reply !
on 23-12-2021 16:34
Thank you for coming back to us.
It looks like it was an SNR issue.
Kind regards,
Zak_M