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:56 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/03/2020 20:32:3 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/03/2020 19:53:3 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/03/2020 04:16:13 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/03/2020 02:44:21 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/03/2020 23:24:8 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/03/2020 22:15:12 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/03/2020 20:50:23 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/03/2020 18:58:29 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/03/2020 18:58:14 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 12:32:22 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 11:42:44 | notice | DHCP 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:44 | Error | DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 10:53:4 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 10:24:27 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 10:03:26 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 09:52:42 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 09:09:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 08:24:10 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2020 05:48:57 | Warning! | 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
on 03-06-2020 19:19
Sorry williambonomo
My normal 'outage checker' is currently down, so to access the info you require I am going to need you respond to my private message.
Regards
Lee
on 03-06-2020 20:40
I got it.
I've replied to your private message.
Thank you.
on 03-06-2020 20:52
Hi there is there any update on this F006805698
or will it be delayed further?
on 03-06-2020 21:49
Just want to confirm that: F007906519 ticket is still active?
Over utilisation in area: 20 (Bromley).
I say this because I recieved multiple text messages last week saying the problem had 'been resolved' for which it has not.
I raised a complaint stating I was not happy with the service (3-4x weeks ago)...the poor network is affecting my work (conference call lag spikes etc)....
REALLY disappointed.
on 04-06-2020 08:07
Hi nsamurai,
Thank you for your post.
I have taken a look into the fault F007906519. The fault is still active.
The current estimated fix time: 17 JUN 2020 09:00.
^Martin
on 04-06-2020 09:47
Hi Martin,
Sorry i know obviously you have done nothing to cause these issues,
hardware faults are just part of the process, but i really gotta know why does the fix dates keep changing, its showing a complete lack of understanding what is going on with their own network, its the same story in each area, they say the fix date, the fix date comes up and then either a new fix date is given or they say it has been fixed when it clearly hasn't
can you offer any insight into this ?
on 04-06-2020 09:48
@martin could you answer my question as well pls. In Bromley too
on 04-06-2020 10:47
Hi whippyice,
I do appreciate this can be frustrating for yourself and other customers affected by this. Any dates we provide for faults are and will always be estimates. That meaning that these dates can change if we are unable to resolve the fault by the initial date provided. Reasons why a date may be extended can vary depending on the situation of the fault. Examples can be such as: If new equipment is needed to be ordered, Availability of engineer, fault is more complex then initially diagnosed, etc
Due the current pandemic fix dates are being affected. I can assure you we are working to resolve any and all faults as soon as possible.
Our apologies for the inconvenience.
^Martin
on 04-06-2020 10:50
on 04-06-2020 11:05
Hi Martin,
Could you please, check F007908422?