on 12-02-2023 18:29
Hello All,
Strange issue I'm having once or twice daily, seemingly at random. My WiFi will drop out on all devices but only for a few seconds then resume normally. However this is quite frustrating as it will be long enough to interrupt a stream or game and cause a dropout.
My network log lists these events that seem to coincide:
No Ranging Response received - T3 time-out
SYNC Timing Synchronization failure - Loss of Sync
these are logged daily usually 2-3 times a day
all downstream/upstream power levels and SNR are in spec and displaying okay.
Router has been reset multiple times and to no avail, my Roku TV also ocassionally really struggles to connec tot the wifi despite the router being in the same room. It will connect play for a few seconds, then drop out again over and over.
Thanks in advance for any help with this it's very frustrating.
Kind Regards,
G
on 13-02-2023 16:22
on 13-02-2023 17:43
Hello mate,
thanks for the help, it's a super hub 3
The QAM values are all 64, the Up/Down error tables are as follows:
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 8 | 0 |
3 | ATDMA | 0 | 0 | 2 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
5 | ATDMA | 0 | 0 | 2 | 0 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.6 | 732 | 5776 |
2 | Locked | 36.6 | 95 | 13427 |
3 | Locked | 36.6 | 112 | 14024 |
4 | Locked | 37.3 | 85 | 14239 |
5 | Locked | 37.3 | 89 | 6186 |
6 | Locked | 37.3 | 91 | 14411 |
7 | Locked | 37.6 | 534 | 13686 |
8 | Locked | 37.3 | 610 | 11410 |
9 | Locked | 37.6 | 629 | 9126 |
10 | Locked | 37.6 | 564 | 9093 |
11 | Locked | 37.6 | 641 | 6210 |
12 | Locked | 37.6 | 750 | 5795 |
13 | Locked | 37.6 | 888 | 6114 |
14 | Locked | 37.6 | 1238 | 4534 |
15 | Locked | 38.6 | 1407 | 4539 |
16 | Locked | 38.6 | 1213 | 4572 |
17 | Locked | 38.6 | 859 | 4609 |
18 | Locked | 38.6 | 2169 | 4986 |
19 | Locked | 38.9 | 3066 | 2787 |
20 | Locked | 38.9 | 3121 | 4876 |
21 | Locked | 38.9 | 2751 | 11829 |
22 | Locked | 38.6 | 2447 | 11804 |
23 | Locked | 38.9 | 2246 | 11889 |
24 | Locked | 38.6 | 7727 | 5385 |
Time Priority Description
13/02/2023 16:57:10 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:45:6 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:45:2 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:45:1 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:45:1 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:59 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:56 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:56 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:55 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:29 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:24 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:24 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:24 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:24 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 11:44:23 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 10:48:9 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 10:48:4 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 10:48:4 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 10:48:4 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2023 10:48:3 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
I'll have a look at settuping that up now thanks mate.
These dropouts only started recentyl and not had any loss of service like this before. I've had one today so far.
Thanks in advance for any other help you can give, it's much appreciated
Kind Regards,
G
on 14-02-2023 01:02
on 14-02-2023 18:13
Hi John,
Thanks again for the help, followed all the additional steps.
The problems seems to have got worse after the reset, even over a wired ethernet connection.
Experiencing a lot of packet loss when video calling and in games.
No Post RS errors yet but started to get new T3 errors, I think I need a VM tech to come out
VM check your router test is higlighting an issue.
Many thanks,
G
on 14-02-2023 18:46
on 16-02-2023 19:01
Hi @gc2049
Welcome to our community forums and sorry to hear you have been having wifi dropouts on your service. We can understand the inconvenience caused and want to help. I have a look into this and I can confirm there is an SNR outage in your area that may be affecting service. Our engineering team is currently working to resolve this and to get the service up and running again. The current estimated fix time is 22 FEB 2023 at 09:00. Please let us know if the issue persists after this and we will do our best to help.
Thanks,