Menu
Reply
  • 15
  • 0
  • 0
londonpb
Joining in
195 Views
Message 11 of 16
Flag for a moderator

Re: Total packet loss, latency issues, netflix buffering

Hi,

been trying to post a reply but not seeming to post...so apologies if this comes multiple times!

1. update of ping/latency/packet loss chart

2. network log, shows errors. might mean something to you experts 🙂

 

Time Priority Description

2018-12-09 06:30:32.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-09 18:13:14.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-09 18:29:26.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 00:18:05.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 01:55:20.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 03:20:31.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 04:03:11.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 04:51:45.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 05:49:00.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 06:00:09.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 06:10:11.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 06:11:33.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 06:23:00.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-10 06:42:56.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-13 10:18:32.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-13 10:18:32.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-13 10:19:21.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-13 10:19:22.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-13 10:53:28.00Warning!TEK Invalid - Invalid Key Sequence Number;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-13 14:58:41.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
BackBack
0 Kudos
Reply
  • 15.2K
  • 653
  • 32
Moderator (Retired) John_G
Moderator (Retired)
173 Views
Message 12 of 16
Flag for a moderator

Re: Total packet loss, latency issues, netflix buffering

Thanks for the update londonpb,

I've just checked and the fault Ralph raised for the issue in your area is under ticket F006776781. This is estimated to close 20th December.


The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply
  • 15
  • 0
  • 0
londonpb
Joining in
164 Views
Message 13 of 16
Flag for a moderator

Re: Total packet loss, latency issues, netflix buffering

Hi John,

Here are some snapshots at 20:50 on 20th Dec.

Not sure this has been fixed? (Says the new technical expert...)

A11A0E24-3717-47FD-812F-1F9F292DE7A1.png5CB99B87-8089-4A9D-8D7A-C08AB0518961.pngE720D743-2AA5-4194-844D-CF725D709382.png

0 Kudos
Reply
  • 15
  • 0
  • 0
londonpb
Joining in
143 Views
Message 14 of 16
Flag for a moderator

Re: Total packet loss, latency issues, netflix buffering

I’m afraid this still has not been resolved. Last night watching Netflix I must have had to reboot/reconnect the internet to the TiVo box about 10 times. 

I only had the virgin tv installed yesterday but the issue is the same as before with my YouView box / smart tv. Error codes on the TiVo box were C133 and N17. 

Photos - the total packet loss spike is probably when the TV box was being installed

25CD7F43-6D7D-4471-9A24-77A9749B635B.pngF5FAFE99-30A0-4030-BA52-E295E49648C7.pngC25D2916-F7C3-4F9D-9F45-A807E87DD434.png260E52E7-D858-4327-837C-91EE67EDC5E2.png60B75F70-5E37-437E-AB2B-54C5CD97DADE.pngAF1CEB5A-5797-4B41-A993-860F4C278D30.png8A12E45E-2BDD-4438-A9B7-351FB2C36286.png

0 Kudos
Reply
  • 72
  • 1
  • 7
andf
Dialled in
139 Views
Message 15 of 16
Flag for a moderator

Re: Total packet loss, latency issues, netflix buffering

Morning All,

I have been experiencing a similar issue for about one week; I have opened a different thread, hoping to spur some actions 🙂

  • 14.59K
  • 432
  • 46
Moderator (Retired) Ralph_R
Moderator (Retired)
119 Views
Message 16 of 16
Flag for a moderator

Re: Total packet loss, latency issues, netflix buffering

Hi londonpb,

Thanks for the update, looks like the problem with high FEC count has returned, I'll flag this again with networks.

Apologies for the disruption.

Ralph_R
Forum Moderator

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply