Menu
Reply
Highlighted
  • 5
  • 0
  • 0
Joining in
321 Views
Message 1 of 3
Flag for a moderator

Random packet loss every day

For a few weeks I've been getting random packet loss throughout the day which is only really noticeable when gaming as it only lasts a few seconds.

I used to run my Super Hub 3 in modem mode connected to Google WiFi but have since reverted back to router mode to try to rule out any other hardware being at fault so my current setup is just my super hub 3 plugged directly into my PS4 and PC. Other 2 ports going to a switch which connects a couple of other devices and a wifi access point.

I've started logging any drops using an application on my PC so this is from running the application this evening so far:

Failure Start               Length
25/10/2019 18:04:23 0:00:07
25/10/2019 18:04:38 0:00:13
25/10/2019 18:05:01 0:00:10
25/10/2019 18:51:15 0:00:11
25/10/2019 19:05:59 0:00:06

It's worth noting that there have been many many issues in my area (area reference 31) over the past year and everyone in our area regularly gets complete internet outages which seem to go on every day for a week or two, then suddenly gets resolved for another few months only to return so it may be related to that.

Thanks!

0 Kudos
Reply
Highlighted
  • 5
  • 0
  • 0
Joining in
319 Views
Message 2 of 3
Flag for a moderator

Re: Random packet loss every day

Didn't let me post this in my main post so here are power levels and network log:

Downstream/Upstream stats + network log below:

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 451000000 1 35 256 qam 6
2 411000000 2 36 256 qam 1
3 419000000 2 36 256 qam 2
4 427000000 2.5 37 256 qam 3
5 435000000 1.9 36 256 qam 4
6 443000000 1 36 256 qam 5
7 459000000 1.2 36 256 qam 7
8 467000000 0.7 37 256 qam 8
9 475000000 -0.2 36 256 qam 9
10 483000000 0 36 256 qam 10
11 491000000 0.7 37 256 qam 11
12 499000000 -0.5 36 256 qam 12
13 507000000 -1.4 37 256 qam 13
14 515000000 0 36 256 qam 14
15 523000000 0 35 256 qam 15
16 531000000 -1.7 35 256 qam 16
17 539000000 -2 36 256 qam 17
18 547000000 -0.7 36 256 qam 18
19 555000000 -1.5 36 256 qam 19
20 563000000 -3 36 256 qam 20
21 571000000 -1.7 36 256 qam 21
22 579000000 -0.4 37 256 qam 22
23 587000000 -1.7 37 256 qam 23
24 595000000 -1.7 35 256 qam 24



Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 35.7 29352 4144
2 Locked 36.6 1071312 4454
3 Locked 36.6 41301 6289
4 Locked 37.3 17206 7134
5 Locked 36.6 286217 7816
6 Locked 36.3 54498 7451
7 Locked 36.6 25002 6858
8 Locked 37.3 301270 9595
9 Locked 36.6 57909 9133
10 Locked 36.3 14554 4503
11 Locked 37.3 8110 4782
12 Locked 37 10321 5845
13 Locked 37.3 78753 7609
14 Locked 36.3 652149 6994
15 Locked 35.7 8326229 6430
16 Locked 35.7 811430 6158
17 Locked 36.3 933879 5170
18 Locked 36.6 34447 5143
19 Locked 36.3 17669 5895
20 Locked 36.6 10155 6149
21 Locked 36.6 84727 5676
22 Locked 37.6 128184 7619
23 Locked 37.3 3091915 5401
24 Locked 35.7 1595789 4952


Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 60299983 4.05 5120 64 qam 1
2 39400014 4 5120 64 qam 4
3 46199981 3.9 5120 64 qam 3
4 53700029 4 5120 64 qam 2



Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0


Network Log
Time Priority Description
25/10/2019 00:12:38 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 00:12:38 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 00:12:45 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 00:12:45 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 14:22:28 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:04:22 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:04:22 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:04:22 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:04:36 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:04:36 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:05:1 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:05:1 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:05:2 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:05:2 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:51:15 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 17:51:15 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 18:05:58 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 18:05:58 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 18:05:58 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2019 18:05:58 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 2.4K
  • 379
  • 930
Problem sorter
285 Views
Message 3 of 3
Flag for a moderator

Re: Random packet loss every day

SNR I believe is just in spec, but looks to be very much at the low end of what you'd want to see, power levels seem within spec, but have quite a wide range from +2.5 to -3, and the error performance is a concern.  Reboot the hub (this should reset the error counters) and see if they keep climbing over the next day or two, if they do hold on until the forum staff come to this post, because you'll need a technician to sort out the line.  In the meanwhile make sure that the connecting cable between hub and wall box is securely tightened at both ends, if it is loose than can cause problems.  I wouldn't be surprised if your speed is a bit down, and latency may be poor due to all the errors.

For comparison, my Hub 3 has a nice even SNR of 38.6 to 38.9 on all channels, power levels +2.9 to +4.5 and the error count after two weeks uptime is about 40 pre-RS (corrected) errors on each channel and a single post RS (uncorrected) error on one channel.

You may also want to set up a Broadband Quality Monitor at Thinkbroadband.com to continuously monitor the performance of the connection.  As that is pinging your Hub 3's modem, it is entirely independent of your wifi arrangements.