Menu
Reply
Highlighted
  • 52
  • 0
  • 6
On our wavelength
416 Views
Message 21 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

Problems seem to have cleared up now, hopefully they won't return.

0 Kudos
Reply
Highlighted
  • 52
  • 0
  • 6
On our wavelength
406 Views
Message 22 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

Spoke too soon, have lost connectivity completely since around 12:30am. Same happened before the weekend but I put it down to a momentary outage since it was back the following day. What is going on?

0 Kudos
Reply
Highlighted
  • 14
  • 0
  • 2
Tuning in
390 Views
Message 23 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

Are you using a VPN?

0 Kudos
Reply
Highlighted
  • 52
  • 0
  • 6
On our wavelength
361 Views
Message 24 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

No not using a VPN, checked service status just before I went to bed and there was a known issue in the area with estimated fix for 5am. All working again now, but it would be nice to have a consistently working service...

0 Kudos
Reply
Highlighted
  • 52
  • 0
  • 6
On our wavelength
339 Views
Message 25 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

Service has gone down 3 times over the course of today.

0 Kudos
Reply
Highlighted
  • 52
  • 0
  • 6
On our wavelength
334 Views
Message 26 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 203000000 7 40 256 qam 9
2 139000000 6.8 38 256 qam 1
3 147000000 7.1 38 256 qam 2
4 155000000 7.1 40 256 qam 3
5 163000000 7.5 40 256 qam 4
6 171000000 7.5 40 256 qam 5
7 179000000 7.5 40 256 qam 6
8 187000000 7.5 40 256 qam 7
9 195000000 7.1 40 256 qam 8
10 211000000 6.5 40 256 qam 10
11 219000000 6.5 40 256 qam 11
12 227000000 6 40 256 qam 12
13 235000000 6.4 40 256 qam 13
14 243000000 6.5 40 256 qam 14
15 251000000 6.6 40 256 qam 15
16 259000000 6.9 40 256 qam 16
17 267000000 7.1 40 256 qam 17
18 275000000 7.3 40 256 qam 18
19 283000000 7.4 40 256 qam 19
20 291000000 7.4 40 256 qam 20
21 299000000 7.5 40 256 qam 21
22 307000000 7 40 256 qam 22
23 315000000 6.6 40 256 qam 23
24 323000000 6.9 40 256 qam 24

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 5 0
2 Locked 38.9 0 0
3 Locked 38.9 5 0
4 Locked 40.3 0 0
5 Locked 40.3 6 0
6 Locked 40.9 17 0
7 Locked 40.3 18 0
8 Locked 40.3 16 0
9 Locked 40.9 3 0
10 Locked 40.3 5 0
11 Locked 40.9 5 0
12 Locked 40.9 0 0
13 Locked 40.3 5 0
14 Locked 40.3 5 0
15 Locked 40.9 3 0
16 Locked 40.3 0 0
17 Locked 40.3 5 0
18 Locked 40.3 5 0
19 Locked 40.9 5 0
20 Locked 40.9 6 0
21 Locked 40.3 0 0
22 Locked 40.9 4 0
23 Locked 40.3 0 0
24 Locked 40.3 5 0

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 46200000 4.1 5120 64 qam 87
2 39400000 4.1 5120 64 qam 88
3 53700000 4.125 5120 64 qam 86
4 60300000 4.25 5120 64 qam 85

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
18/03/2020 21:30:9 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:29:26 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:27:8 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:27:4 Warning! LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:23:34 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:23:34 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:23:34 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:23:32 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:23:27 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 21:23:27 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 17:09:32 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 17:03:41 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 17:03:40 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 17:03:35 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 17:03:34 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 17:03:34 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 14:51:28 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 14:51:24 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 14:51:24 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 14:51:24 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;



0 Kudos
Reply
Highlighted
  • 4.23K
  • 169
  • 233
Forum Team
Forum Team
329 Views
Message 27 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

Hi norf3n,

 

Thank you for your post. I'm sorry to hear you're having this issue. 

 

I have had a check on our side and it is showing that we do have a fault reported and our engineers are working to get this resolved asap. 

 

The current estimated fix time is 18 MAR 2020 23:00.

 

^Martin

0 Kudos
Reply
Highlighted
  • 52
  • 0
  • 6
On our wavelength
312 Views
Message 28 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

Just went down again

0 Kudos
Reply
Highlighted
  • 723
  • 33
  • 70
Forum Team
Forum Team
288 Views
Message 29 of 29
Flag for a moderator

Re: Return of lag spikes and packet loss (GL Area)

Thank you for coming back to us @norf3n 

 

How are things looking so far this morning? 

 

Kind Regards 

Zak_M 

0 Kudos
Reply