Menu
Reply
Highlighted
  • 131
  • 3
  • 15
Up to speed
376 Views
Message 1 of 7
Flag for a moderator

Constant packet loss (Area 15)

There was a serious outage on the 3rd April around midnight that knocked me (and seemingly a lot of others) offline. Internet came back around 1:00am and my IP had been changed (I have been running BQM on previous IP since previous Virgin issues). I am unsure of when the packetloss started, but since yesterday, I have had a BQM setup and am receiving constant packet loss.

Area 15 (NW5)
Wired Connection
SuperHub 2ac
All wires/connections checked
No known issues on status

BQM:
e2348d659ad12c6cfe7e4c9ab7d616ea7b4d5cc9-06-04-2020

Downstream:

 DS-1DS-2DS-3DS-4DS-5DS-6DS-7DS-8
Frequency (Hz)259000000203000000211000000219000000227000000235000000243000000251000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID169101112131415
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)3.103.523.573.553.493.343.253.13
RxMER (dB)37.3637.6437.6437.0937.6437.9437.9437.94
Pre RS Errors2364422225222432313220267199291980720130
Post RS Errors1653615149152041552113351136221341513658


Upstream:

 US-1US-2US-3US-4
Channel Type2.02.02.02.0
Channel ID1432
Frequency (Hz)60300000394000004620000053700000
Ranging StatusSuccessAbortedSuccessAborted
Modulation16QAM16QAM16QAM16QAM
Symbol Rate (Sym/sec)5120000512000051200005120000
Mini-Slot Size2222
Power Level (dBmV)40.4645.9645.9647.46
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts3431150916161465
T4 Timeouts0000


Network Log:

First TimeLast TimePriorityError NumberDescription
06/04/2020 17:52:05 GMT06/04/2020 17:52:05 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:52:03 GMT06/04/2020 17:52:03 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:52:02 GMT06/04/2020 17:52:02 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:50:44 GMT06/04/2020 17:50:44 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:50:23 GMT06/04/2020 17:50:23 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:50:22 GMT06/04/2020 17:50:22 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:50:07 GMT06/04/2020 17:50:07 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:49:05 GMT06/04/2020 17:49:05 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:46:02 GMT06/04/2020 17:46:02 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:45:53 GMT06/04/2020 17:45:53 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:45:52 GMT06/04/2020 17:45:52 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:45:47 GMT06/04/2020 17:45:47 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:45:24 GMT06/04/2020 17:45:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:45:14 GMT06/04/2020 17:45:14 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:45:11 GMT06/04/2020 17:45:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:45:05 GMT06/04/2020 17:45:05 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:45:04 GMT06/04/2020 17:45:04 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:42:26 GMT06/04/2020 17:42:26 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:42:25 GMT06/04/2020 17:42:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/04/2020 17:42:24 GMT06/04/2020 17:42:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out


Ping BBC.co.uk
Ping statistics for 151.101.128.81:
Packets: Sent = 50, Received = 44, Lost = 6 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 51ms, Average = 25ms

Any tests missing?

0 Kudos
Reply
Highlighted
  • 131
  • 3
  • 15
Up to speed
338 Views
Message 2 of 7
Flag for a moderator

Re: Constant packet loss (Area 15)

Any one at all?

66d1658f11a3657b7c4333aef45b599d4df7d1ab-07-04-2020

Router put into Modem mode at around 12am to test, no difference so reverted back.
Since the details above have also changed, I figure I will post the new results.
The only thing unchanged is the constant T3 Time-outs

 DS-1DS-2DS-3DS-4DS-5DS-6DS-7DS-8
Frequency (Hz)259000000203000000211000000219000000227000000235000000243000000251000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID169101112131415
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)2.913.423.343.193.132.972.942.93
RxMER (dB)37.0937.3637.6437.0937.9437.9437.9437.94
Pre RS Errors13139122191291613570129901140875085958
Post RS Errors10422930810205108701032387294846

3277

 

 US-1US-2US-3US-4
Channel Type2.02.02.02.0
Channel ID5643
Frequency (Hz)32600000258000003940000046200000
Ranging StatusSuccessSuccessSuccessSuccess
Modulation16QAM32QAM16QAM16QAM
Symbol Rate (Sym/sec)5120000512000051200005120000
Mini-Slot Size2222
Power Level (dBmV)41.0040.5041.7541.00
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts1131021927
T4 Timeouts0000

 

First TimeLast TimePriorityError NumberDescription
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
07/04/2020 13:38:25 GMT07/04/2020 13:38:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out

 

0 Kudos
Reply
Highlighted
  • 131
  • 3
  • 15
Up to speed
325 Views
Message 3 of 7
Flag for a moderator

Re: Constant packet loss (Area 15)

As an addition, Virgin Status page is now listed a fault with estimated repair at 18:00 today.
Still welcome someone with the knowledge of what any of it means, to take a look at the above data.

Thank you.
0 Kudos
Reply
Highlighted
  • 131
  • 3
  • 15
Up to speed
304 Views
Message 4 of 7
Flag for a moderator

Re: Constant packet loss (Area 15)

Fault F007934419 resolved. Problem possbily improved but still continues.
No responses, will give twitter a try I guess.

66d1658f11a3657b7c4333aef45b599d4df7d1ab-07-04-2020

0 Kudos
Reply
Highlighted
  • 131
  • 3
  • 15
Up to speed
271 Views
Message 5 of 7
Flag for a moderator

Re: Constant packet loss (Area 15)

Another update, seemingly for record purposes only.

Service status has a new fault listed for repair again today @ 18:00

Still constant packetloss.

63971daa59c90ce60d944436b31c0b91e9c90139-08-04-2020

0 Kudos
Reply
Highlighted
  • 131
  • 3
  • 15
Up to speed
252 Views
Message 6 of 7
Flag for a moderator

Re: Constant packet loss (Area 15)

Just another update in my thread of loneliness and digital self-isolation.
Do any of the work-from-home Virgin Staff fancy having at least a glance in this general direction?

It is getting more and more frustrating to see that people are being replied to within 15 minutes to a couple of hours for similar issues and yet I have been waiting for around three days without even an acknowledgement. Even if you tell me I have to wait 6 months for some resolution, at least I wouldn't feel like I was being ignored.

Fault: F007937080 fixed.
My internet: not fixed.

63971daa59c90ce60d944436b31c0b91e9c90139-08-04-2020

 

0 Kudos
Reply
Highlighted
  • 131
  • 3
  • 15
Up to speed
230 Views
Message 7 of 7
Flag for a moderator

Re: Constant packet loss (Area 15)

Yet another new fault is listed on the Service Status.

I wonder if they will close this one early and say it's fixed only to open again tomorrow.

BQM as per usual, a lot less red this morning, shame about the giant peaks of blue and the background being entirely yellow.
45c0984bbbd5d02cfa646a27fcd77061dd14bf10-09-04-2020

Ping statistics for 151.101.0.81:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 3883ms, Average = 121ms

 

0 Kudos
Reply