Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Ping, packet loss and Latency all over the place. Can we get some info please!

CloudchaserXI
Up to speed

on ‎20-03-2020 21:03

Started 2 days ago - I'm assuming this is Covid 19 related? If it is PLEASE confirm Virgin.

380Meg fibre, all networked - pc direct to Hub 3.

All of a sudden: massive lag spikes, interruption, packet loss.

I have tried Modem mode. Tried to reset router. 

Software version: 9.1.1811.401

 

 

Log below:

20/03/2020 20:32:56noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2020 20:32:3Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2020 19:53:3noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2020 04:16:13Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2020 02:44:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 23:24:8Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 22:15:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 20:50:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 18:58:29noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2020 18:58:14Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 12:32:22Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 11:42:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 11:42:44ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 10:53:4ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 10:24:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 10:03:26ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 09:52:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 09:09:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 08:24:10ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2020 05:48:57Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

PING google.com (216.58.210.238): 64 data bytes
72 bytes from 216.58.210.238: seq=0 ttl=55 time=20.000 ms
72 bytes from 216.58.210.238: seq=1 ttl=55 time=10.000 ms
72 bytes from 216.58.210.238: seq=2 ttl=55 time=4500.000 ms
--- google.com ping statistics ---
5 packets transmitted, 3 packets received, 40% packet loss
round-trip min/avg/max = 10.000/1510.000/4500.000 ms

 

802 REPLIES 802

ejw93
Tuning in
In response to Steven_L

‎05-05-2020 11:15 - edited ‎05-05-2020 11:23

@Steven_L

Still no improvement as of 11am. Area ref 04

 

ejw93_6-1588673738980.png

 

0 Kudos

lukescully
Dialled in
In response to ejw93

on ‎05-05-2020 12:04

Every1 keep updates here goin. My upstream has been done from 51 to 43 finally. Area congestion due resolve 11thmay

0 Kudos

OneEyedPhilly
On our wavelength
In response to lukescully

on ‎05-05-2020 15:19

Need support here too. DN2 area.

Here's yesterdays BQM: https://www.thinkbroadband.com/broadband/monitoring/quality/view/0f9f6c024b073d9efc785db365fead6a20b... 

My post from a couple of weeks ago: https://community.virginmedia.com/t5/Gaming-Support/Latency/td-p/4226077 

Been like this since December everyday nearly, just got worst since lockdown. 

Thanks

0 Kudos

lukescully
Dialled in
In response to OneEyedPhilly

on ‎05-05-2020 15:35

Same here dude. 11th may due to fix area congestion. So far 1 issue done but still worried about my errors mounting up

0 Kudos

OneEyedPhilly
On our wavelength
In response to lukescully

on ‎05-05-2020 15:50

What 11th May nationwide fix?
0 Kudos

ejw93
Tuning in
In response to OneEyedPhilly

on ‎05-05-2020 16:09

Here's my status after the supposed 9am fix on my area this morning. No better. Could someone provide an update please?  

ejw93_0-1588691202463.png

 

0 Kudos

olliey
Joining in

on ‎05-05-2020 16:21

Was promised fix for congestion in area 31 (Northampton) by yesterday. This has either not been done or not worked.

Still experiencing significant congestion:

PING www.google.com (216.58.204.4): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 216.58.204.4: icmp_seq=1 ttl=54 time=113.580 ms
64 bytes from 216.58.204.4: icmp_seq=2 ttl=54 time=141.710 ms
64 bytes from 216.58.204.4: icmp_seq=3 ttl=54 time=45.809 ms
64 bytes from 216.58.204.4: icmp_seq=4 ttl=54 time=21.950 ms
64 bytes from 216.58.204.4: icmp_seq=5 ttl=54 time=61.994 ms
64 bytes from 216.58.204.4: icmp_seq=6 ttl=54 time=46.566 ms
64 bytes from 216.58.204.4: icmp_seq=7 ttl=54 time=122.405 ms
64 bytes from 216.58.204.4: icmp_seq=8 ttl=54 time=47.938 ms
64 bytes from 216.58.204.4: icmp_seq=9 ttl=54 time=76.498 ms
64 bytes from 216.58.204.4: icmp_seq=10 ttl=54 time=109.007 ms
64 bytes from 216.58.204.4: icmp_seq=11 ttl=54 time=75.060 ms
64 bytes from 216.58.204.4: icmp_seq=12 ttl=54 time=205.089 ms
64 bytes from 216.58.204.4: icmp_seq=13 ttl=54 time=70.215 ms
64 bytes from 216.58.204.4: icmp_seq=14 ttl=54 time=37.699 ms
64 bytes from 216.58.204.4: icmp_seq=15 ttl=54 time=30.759 ms
64 bytes from 216.58.204.4: icmp_seq=16 ttl=54 time=53.720 ms
64 bytes from 216.58.204.4: icmp_seq=17 ttl=54 time=55.482 ms
64 bytes from 216.58.204.4: icmp_seq=18 ttl=54 time=111.451 ms
64 bytes from 216.58.204.4: icmp_seq=19 ttl=54 time=34.876 ms
64 bytes from 216.58.204.4: icmp_seq=20 ttl=54 time=60.249 ms
64 bytes from 216.58.204.4: icmp_seq=21 ttl=54 time=149.131 ms
64 bytes from 216.58.204.4: icmp_seq=22 ttl=54 time=79.647 ms
64 bytes from 216.58.204.4: icmp_seq=23 ttl=54 time=179.942 ms
64 bytes from 216.58.204.4: icmp_seq=24 ttl=54 time=116.024 ms
^C
--- www.google.com ping statistics ---
25 packets transmitted, 24 packets received, 4.0% packet loss
round-trip min/avg/max/stddev = 21.950/85.283/205.089/47.732 ms

 

0 Kudos

jackgf
On our wavelength
In response to olliey

on ‎05-05-2020 16:24

I have been 2 months with consistent minimum 20% packet loss all day.
5 engineer visits no fix.

I have now left VM.

JA_Foster
Joining in

on ‎05-05-2020 16:28

I'll try again since I was ignored on my own post and the last time I asked in this thread....

When is the utilisation issue going to be fixed for the SM5 postcode?

Thanks in advance

0 Kudos

hortonj88
Fibre optic
In response to jackgf

on ‎05-05-2020 19:14

I thought Openreach have halted installations until 1st June?

 

 



********************************************************
Left Virgin Media in 2020 after being fobbed off one too many times about over utilisation.


Now: BT FTTP 900/110 connected an ASUS RT-AC86U router.


https://www.speedtest.net/result/12098955842.png
0 Kudos
Top