Is it me or is everyone in this area having terrible experience? I live in Irvine, CA
I pay for the 50Megabit down connection (preferred). Every few weeks there is either an outage or terrible speeds. Currently (2 days now) I am getting ping timeouts every 5 to 10 pings to sites like google.
Ping statistics for 8.8.8.8:
Packets: Sent = 936, Received = 687, Lost = 249 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 67ms, Average = 18ms
Ping statistics for 64.91.255.98:
Packets: Sent = 977, Received = 745, Lost = 232 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 138ms, Average = 92ms
Ping statistics for 206.190.36.45:
Packets: Sent = 983, Received = 761, Lost = 222 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 100ms, Average = 53ms
Ping statistics for 157.166.226.25:
Packets: Sent = 951, Received = 706, Lost = 245 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 107ms, Average = 70ms
Speed tests show my connection at sub 1 Megabit. Called COX last night about this, everything is perfect on their side, no outages, have a tech coming tomorrow. Except I had a tech out 6 months ago for similar issue, he reported the line and equipment is in perfect working order.
Speed test result - http://www.speedtest.net/result/4947150255.png
Restarting modem, router using different PCs make no difference (everything is wired). Cable modem is a Motorolla SB6141. Reporting the following:
http://i.imgur.com/jt69h9s.png
The Downdetector site (not sure how reliable it is) shows the following:
http://i.imgur.com/P69KOIS.png
If it is accurate, how can they possibly report "no outages" ???
This is so freaking frustrating... I have a tech coming tomorrow at 6PM, there is no issue here, the issue is with COX's service something outside my house.... Am I the only one that goes through this every couple of months?
This is the modem log, starting with manual reset (power pull):
Dec 26 2015 19:55:17 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:28:38 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:28:08 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:27:48 5-Warning U102.0 TCS Partial Service;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:27:48 5-Warning U103.0 Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:27:37 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:26:47 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:26:47 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:26:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:26:04 3-Critical I02.0 REG RSP not received;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:26:04 4-Error I271.0 T6 Timeout and retries exceeded;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:26:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:25:52 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Dec 26 2015 19:25:52 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:13:5f:02:9c:9c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=78:96:84:f9:e1:5a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
↧