Menu
Reply
CleverTortoise
  • 17
  • 0
  • 3
On our wavelength
961 Views
Message 1 of 6
Flag for a moderator

Recent extreme ping since COVID lockdown

Hardware:

Superhub 2ac in modem mode 
Software Version "V2.01.15"
Hardware Version 1.03


ASUS RT-AC86U router
Current Version : 3.0.0.4.384_81352-g9910ab0


TP-link TLPA411 nano powerline adapter
firmware 1.3.1.2141-00_401092_160622_902

 

BQM LINK

PingPlotter 10 min snapshot 1

PingPlotter 10 min snapshot 2

 

Every device on the network suffers from multiple ping spikes in a 60-second range constantly.

The pc directly connected to the router also suffers these constant ping spikes.

I've connected 1 device directly to the modem and still suffer these spikes. 

I've factory reset the modem and tried it in router mode, still suffer these spikes.

 

The network becomes stable after 12pm with no spikes until the next morning roles around and the spikes crop up again. This all started when the lockdown was announced just over a week ago...


 

0 Kudos
Reply
alfiebench
  • 24
  • 0
  • 1
Tuning in
928 Views
Message 2 of 6
Flag for a moderator

Re: Recent extreme ping since COVID lockdown

having the same issue for about a week, ran a ping through multiple servers and the packet loss was happening on virgins servers, guess they're struggling to cope with the extra demand which sucks, been trying to play CS with packet loss every few minutes or so, dies down a lot past 12 but still there although its still effecting game play and literally unplayable in the day.

0 Kudos
Reply
CleverTortoise
  • 17
  • 0
  • 3
On our wavelength
788 Views
Message 3 of 6
Flag for a moderator

Re: Recent extreme ping since COVID lockdown

I'm glad to see this problem still persists after six months!

My Broadband Ping - home home

Great service as usual VM. Charging me the full amount for an unusable connection!

0 Kudos
Reply
Anonymous
Not applicable
772 Views
Message 4 of 6
Flag for a moderator

Re: Recent extreme ping since COVID lockdown

Could you access your router using http://192.168.0.1/ or http://192.168.100.1 for modem mode . Don't log in, select the 'Check Router Status' option and paste your 'Downstream', 'Upstream', and 'Network Log' tabs?

At least we can check the stats to rule out an issue with the line.

0 Kudos
Reply
CleverTortoise
  • 17
  • 0
  • 3
On our wavelength
708 Views
Message 5 of 6
Flag for a moderator

Re: Recent extreme ping since COVID lockdown

DOWNSTREAM

 

 

DS-1

DS-2

DS-3

DS-4

DS-5

DS-6

DS-7

DS-8

Frequency (Hz)

298750000

266750000

274750000

282750000

290750000

306750000

314750000

322750000

Lock Status(QAM Lock/FEC Sync/MPEG Lock)

Locked

Locked

Locked

Locked

Locked

Locked

Locked

Locked

Channel ID

21

17

18

19

20

22

23

24

Modulation

256QAM

256QAM

256QAM

256QAM

256QAM

256QAM

256QAM

256QAM

Symbol Rate (Msym/sec)

6.952000

6.952000

6.952000

6.952000

6.952000

6.952000

6.952000

6.952000

Interleave Depth

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

I=12

J=17

Power Level (dBmV)

-0.11

-1.74

-1.55

-1.20

-0.66

0.19

0.37

0.72

RxMER (dB)

36.84

35.97

35.97

36.17

36.84

36.84

38.26

38.61

Pre RS Errors

278

286

303

294

301

1093

977

983

Post RS Errors

275

277

301

293

288

1093

977

983



UPSTREAM

 

US-1 US-2 US-3 US-4

Channel Type 2.0 2.0 2.0 2.0

Channel ID 2 4 3 1

Frequency (Hz) 53700000 39400000 46200000 60300000

Ranging Status Success Success Success Success

Modulation 64QAM 64QAM 64QAM 64QAM

Symbol Rate (Sym/sec) 5120000 5120000 5120000 5120000

Mini-Slot Size 2 2 2 2

Power Level (dBmV) 48.25 48.25 48.25 48.25

T1 Timeouts 0 0 0 0

T2 Timeouts 0 0 0 0

T3 Timeouts 0 0 0 0

T4 Timeouts 0 0 0 0






13/08/2020 11:54:48 GMT

13/08/2020 11:54:48 GMT

Warning (5)

66050310

Auth Success - Web login successful.

13/08/2020 11:51:10 GMT

13/08/2020 11:51:10 GMT

Error (4)

68000407

TOD established

Time Not Established

Time Not Established

Notice (6)

84000510

Downstream Locked Successfully

13/08/2020 11:44:34 GMT

13/08/2020 11:44:34 GMT

Error (4)

68000407

TOD established

Time Not Established

Time Not Established

Notice (6)

84000510

Downstream Locked Successfully

13/08/2020 11:37:30 GMT

13/08/2020 11:37:30 GMT

Error (4)

68000407

TOD established

Time Not Established

Time Not Established

Notice (6)

84000510

Downstream Locked Successfully

13/08/2020 10:42:06 GMT

13/08/2020 10:42:06 GMT

Notice (6)

68010600

DHCP Renew - lease parameters tftp file-******** modified

13/08/2020 10:42:06 GMT

13/08/2020 10:42:06 GMT

Error (4)

68010400

DHCP REBIND WARNING - Field invalid in response

13/08/2020 10:41:14 GMT

13/08/2020 10:41:14 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 10:40:24 GMT

13/08/2020 10:40:24 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 10:38:45 GMT

13/08/2020 10:38:45 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 10:35:26 GMT

13/08/2020 10:35:26 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 10:28:49 GMT

13/08/2020 10:28:49 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 10:15:36 GMT

13/08/2020 10:15:36 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 09:49:10 GMT

13/08/2020 09:49:10 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 08:56:18 GMT

13/08/2020 08:56:18 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 07:10:33 GMT

13/08/2020 07:10:33 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

13/08/2020 03:39:03 GMT

13/08/2020 03:39:03 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

12/08/2020 20:36:04 GMT

12/08/2020 20:36:04 GMT

Error (4)

68010100

DHCP RENEW sent - No response for IPv4

 

0 Kudos
Reply
Andrew-G
  • 6.08K
  • 1.07K
  • 2.56K
Very Insightful Person
Very Insightful Person
701 Views
Message 6 of 6
Flag for a moderator

Re: Recent extreme ping since COVID lockdown

I'm glad to see this problem still persists after six months!

Your BQM is pretty conclusive proof that you're on a part of VM's network that is suffering from over-utilisation.  My understanding of what this means for you is similar to this previous example.  

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply