Not applicable

Speed Problem - packet loss

Hello,

 

I've been suffering Internet problems for a week.  About 7 days ago I was playing LOL at night, my ping was like normal (60 - 70) but I can felt there might be awful packet loss problem.  (My ping did not flutuated but I was still terribly lagging.)  After that night my access has became a nightmare, I've tried some other online games and met similar situations (except last Saturday night, it was as good as before, but only one night).  Webs like twitch is not smooth as well.  Usually this problem happens at nights but this afternoon I lose connection like every 5 minutes.  I can't even finish the "speed test" on TWC website, I have tried 5 times and it's said "time out".

 

So I checked my modem (Arris).  Really wonder what's the problem. Smiley Sad

 

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 113687.00 MHz-7.20 dBmV38.98 dB256QAM118244327426502703
Downstream 21615.00 MHz-5.00 dBmV40.37 dB256QAM110262733131312931831
Downstream 32621.00 MHz-4.80 dBmV40.37 dB256QAM10966198259919422660
Downstream 43627.00 MHz-5.70 dBmV38.98 dB256QAM1072236066035531841
Downstream 54633.00 MHz-5.60 dBmV38.98 dB256QAM108543984121607819727
Downstream 65639.00 MHz-5.00 dBmV38.98 dB256QAM981944336720487906
Downstream 76645.00 MHz-5.20 dBmV40.37 dB256QAM95701553981865813711
Downstream 87651.00 MHz-5.90 dBmV38.98 dB256QAM93091430681441419053
Downstream 98657.00 MHz-5.90 dBmV40.37 dB256QAM9440546349551117158
Downstream 109663.00 MHz-6.30 dBmV38.98 dB256QAM9743489276507316784
Downstream 1110669.00 MHz-7.20 dBmV38.98 dB256QAM9804032059149777893
Downstream 1211675.00 MHz-7.40 dBmV38.98 dB256QAM101503177621617618736
Downstream 1312681.00 MHz-7.00 dBmV38.98 dB256QAM10977732790286412078
Downstream 1414693.00 MHz-7.30 dBmV38.98 dB256QAM111522881391700412265
Downstream 1515699.00 MHz-7.00 dBmV38.61 dB256QAM11082137317375112077
Downstream 1616705.00 MHz-6.70 dBmV40.37 dB256QAM10559250023354416238

 

 

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1437.00 MHz52.00 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Upstream 2330.60 MHz42.50 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 3223.30 MHz42.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 4118.50 MHz41.00 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 

 Status
System Uptime:43 d: 7 h: 09 m
Computers Detected:staticCPE(2), dynamicCPE(0)
CM Status:Telephony-Reg Complete
Time and Date:Fri 2016-05-13 00:19:45

 

DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
5/5/2016 19:02820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:02820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:02840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:02820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:02840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:02820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:02840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:02820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:03820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:03840007005RCS Partial Service;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:03820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:16820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:16840007005RCS Partial Service;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/5/2016 19:40820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/8/2016 14:00680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/8/2016 14:00680106006DHCP Renew - lease parameters time server-76.85.237.69;tftp file-?BEWGlyTUBZguENIK+5Yw@CvuWMA4R8bEEyKpBC5OppazASHddnO9e modified;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/8/2016 14:06820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/12/2016 2:00680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/12/2016 2:00680106006DHCP Renew - lease parameters time server-76.85.237.29;tftp file-?BEWGlyTUBZguENIK+5Yw@CvuWMGqdmxXRx67Vnc042sAGcmVNhdlu modified;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;
5/12/2016 2:01820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:2e:10:d2;CMTS-MAC=00:01:5c:69:ac:6a;CM-QOS=1.1;CM-VER=3.0;

 

 

 PacketCable(MTA) Events

 

Date TimeEvent IDDescription
3/30/2016 16:5816MTA TFTP: Successful
3/30/2016 16:5826MTA PROV: Successful!
3/30/2016 16:583Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
3/30/2016 17:0914Power Supply Telemetry Log - BATTERY MISSING
3/30/2016 17:0916MTA TFTP: Successful
3/30/2016 17:0926MTA PROV: Successful!
3/30/2016 17:093Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
3/30/2016 17:1314Power Supply Telemetry Log - BATTERY MISSING
3/30/2016 17:1316MTA TFTP: Successful
3/30/2016 17:1326MTA PROV: Successful!
3/30/2016 17:133Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/1/2016 19:314000960006New time has been retrieved from ToD server.
4/5/2016 7:314000960006New time has been retrieved from ToD server.
4/8/2016 19:314000960006New time has been retrieved from ToD server.
4/12/2016 7:314000960006New time has been retrieved from ToD server.
4/15/2016 19:314000960006New time has been retrieved from ToD server.
4/19/2016 7:314000960006New time has been retrieved from ToD server.
4/24/2016 22:173Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
4/24/2016 22:2214Power Supply Telemetry Log - BATTERY MISSING
4/24/2016 22:2216MTA TFTP: Successful
4/24/2016 22:2226MTA PROV: Successful!
4/24/2016 22:223Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/27/2016 8:564000960006New time has been retrieved from ToD server.
4/30/2016 20:564000960006New time has been retrieved from ToD server.
5/4/2016 8:564000960006New time has been retrieved from ToD server.
5/5/2016 19:033Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
5/5/2016 19:0416MTA TFTP: Successful
5/5/2016 19:0426MTA PROV: Successful!
5/5/2016 19:043Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
5/5/2016 19:0414Power Supply Telemetry Log - BATTERY MISSING
5/8/2016 14:004000960006New time has been retrieved from ToD server.
5/12/2016 2:004000960006New time has been retrieved from ToD server.
5 REPLIES 5
Spectator

Re: Speed Problem - packet loss

I have had the same issues after 8pm every night for the past few weeks, every time I call they sched a tech and I get a call a day before the tech comes out saying they think they fixed it issue and sure enough its fixed for a month then comes back. It's been like this for like 6 months or so. I think they have something they keep patching up vs replacing in my opinion.

 

Also the TWC chat rep I'm on with is saying its a "weak signal..."

 

RF Parameters

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 112837.00 MHz4.00 dBmV38.98 dB256QAM10498929145286019516
Downstream 21771.00 MHz7.20 dBmV40.37 dB256QAM108946670033275299
Downstream 32777.00 MHz7.00 dBmV40.37 dB256QAM1116229431760611265
Downstream 43783.00 MHz6.00 dBmV40.37 dB256QAM111277434366862070
Downstream 54789.00 MHz5.90 dBmV38.98 dB256QAM109247638908764064
Downstream 65795.00 MHz6.00 dBmV40.37 dB256QAM1122556794410547251
Downstream 76801.00 MHz6.20 dBmV40.37 dB256QAM11619604313181712167
Downstream 87807.00 MHz5.40 dBmV40.37 dB256QAM11049239240311814093
Downstream 98813.00 MHz5.30 dBmV38.98 dB256QAM10448682362329314307
Downstream 109819.00 MHz5.00 dBmV40.37 dB256QAM843142842225776675
Downstream 1110825.00 MHz5.20 dBmV38.98 dB256QAM88718009977271100
Downstream 1211831.00 MHz4.70 dBmV38.98 dB256QAM8709970780309714324
Downstream 1313843.00 MHz4.30 dBmV38.98 dB256QAM8822020508324915896
Downstream 1414849.00 MHz4.00 dBmV38.98 dB256QAM9005779650313710374
Downstream 1515855.00 MHz4.00 dBmV38.61 dB256QAM9180168132403118520
Downstream 1616861.00 MHz3.40 dBmV38.61 dB256QAM9702295943174126416
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 19130.60 MHz42.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s16QAM
Upstream 29237.00 MHz43.75 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s16QAM
Upstream 39024.20 MHz41.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s16QAM
Upstream 48919.40 MHz41.50 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Participant

Re: Speed Problem - packet loss

I had the same issue.  I noticed some slowness about 3-4 months ago, but a week ago it got so bad that our 2 Roku's would stop restart.  Doing the TWC speedtest would not complete.  I ran the DSLReports smokeping tool for 24 hours first and it was interestingthat 3 different sources all would get pretty consistent dropped packets from about 3-4 PM till about midnight.  It averaged about 20% loss during that period with some tests getting 100% loss. 

A tech came out on Wednesday and of course did not see anythign in my house or to the pole.  However, there was an issue his supervisor found that related to the node from a nearby neighborhood was misbehaving (don't have the details yet) and causing traffic to be much greater than it should be at my node.  Maintenance fixed it yesterday afternoon, and I have ran from about 12 hours from 2PM yesterday and essentially zero packet loss.  At least only one of the 3 test sources might have a drop or two, but the others woudl not, so probably route related.  In any case worked great last night and working great tonight.  I would also recommend looking at the DSLreports Line Quality test as that will see the drops and tell you where they dropped.  Here is my line quality test that had the most drops and if you scroll down you can see which server experienced the drop (in my case rr.com)

http://www.dslreports.com/pingtest/nil/3376484

 

Hope this helps.

Ron

 

Highlighted
Not applicable

Re: Speed Problem - packet loss

 Thank you so much ronner !

 

I ran the test on this web and the loss is terrifying (15%/30%/22%/28%).  Though my Smokeping test has just begun I guess I have to call a TWC maintenance.

 

Thank you again !

Participant

Re: Speed Problem - packet loss

Good luck on getting it done.  I did not call in maintenace, I felt very fortunate because after the tech could find no reason for what I was seeing, his supervisor had his act together and got maint on it.  In the bottom half of the Line Quality test, it shows where the drops occur (loss column) Check to see if there is any consistency between the different locations the test runs from and that may isolate where the main loss is coming from (likely a rr.com or other twc site)

Best,

Ron

Expert

Re: Speed Problem - packet loss

You have marginal levels and Ingress from broadcast TV.

 The modem should be on no splitter if internet only or the first 2 way splitter if cable tv, All connections must be tight