Author Topic: Internet Connection Performance  (Read 462 times)

colossus972

  • Newbie
  • *
  • Posts: 35
    • View Profile
Internet Connection Performance
« on: January 22, 2012, 11:44:47 AM »
I am seeing high ping times and timeouts. This is causing poor video\gaming\work performance. This problem appears to have started within the last few days. I was hoping mediacom would have resolved it by now..but I guess I need to report it. I live in Geneseo IL 61254. I have restarted the router and the modem. I will attach a screenshot of the modem signal info....and here is a sample ping:

Pinging any-fp3-real.wa1.b.yahoo.com [98.139.180.149] with 32 bytes of data:
Reply from 98.139.180.149: bytes=32 time=82ms TTL=49
Request timed out.
Reply from 98.139.180.149: bytes=32 time=168ms TTL=47
Reply from 98.139.180.149: bytes=32 time=325ms TTL=49
Reply from 98.139.180.149: bytes=32 time=173ms TTL=49
Reply from 98.139.180.149: bytes=32 time=92ms TTL=47
Request timed out.
Reply from 98.139.180.149: bytes=32 time=581ms TTL=49
Reply from 98.139.180.149: bytes=32 time=639ms TTL=49
Reply from 98.139.180.149: bytes=32 time=719ms TTL=49
Request timed out.
Reply from 98.139.180.149: bytes=32 time=406ms TTL=49
Reply from 98.139.180.149: bytes=32 time=118ms TTL=47
Reply from 98.139.180.149: bytes=32 time=306ms TTL=49
Request timed out.
Reply from 98.139.180.149: bytes=32 time=201ms TTL=49
Reply from 98.139.180.149: bytes=32 time=389ms TTL=47
Reply from 98.139.180.149: bytes=32 time=374ms TTL=49
Reply from 98.139.180.149: bytes=32 time=174ms TTL=47
Reply from 98.139.180.149: bytes=32 time=114ms TTL=49
Reply from 98.139.180.149: bytes=32 time=382ms TTL=47
Reply from 98.139.180.149: bytes=32 time=450ms TTL=47
Reply from 98.139.180.149: bytes=32 time=568ms TTL=49
Reply from 98.139.180.149: bytes=32 time=387ms TTL=49
Reply from 98.139.180.149: bytes=32 time=166ms TTL=47
Reply from 98.139.180.149: bytes=32 time=211ms TTL=49
Reply from 98.139.180.149: bytes=32 time=257ms TTL=49
Reply from 98.139.180.149: bytes=32 time=110ms TTL=47
Reply from 98.139.180.149: bytes=32 time=68ms TTL=49
Reply from 98.139.180.149: bytes=32 time=82ms TTL=47
Reply from 98.139.180.149: bytes=32 time=87ms TTL=49
Reply from 98.139.180.149: bytes=32 time=92ms TTL=49
Reply from 98.139.180.149: bytes=32 time=64ms TTL=47
Reply from 98.139.180.149: bytes=32 time=62ms TTL=49
Reply from 98.139.180.149: bytes=32 time=101ms TTL=47
Reply from 98.139.180.149: bytes=32 time=242ms TTL=47
Reply from 98.139.180.149: bytes=32 time=299ms TTL=49
Reply from 98.139.180.149: bytes=32 time=295ms TTL=47
Reply from 98.139.180.149: bytes=32 time=160ms TTL=49
Reply from 98.139.180.149: bytes=32 time=149ms TTL=47
Request timed out.
Reply from 98.139.180.149: bytes=32 time=122ms TTL=49
Reply from 98.139.180.149: bytes=32 time=238ms TTL=49
Reply from 98.139.180.149: bytes=32 time=360ms TTL=47
Reply from 98.139.180.149: bytes=32 time=294ms TTL=49
Reply from 98.139.180.149: bytes=32 time=106ms TTL=47
Reply from 98.139.180.149: bytes=32 time=141ms TTL=49
Request timed out.
Reply from 98.139.180.149: bytes=32 time=185ms TTL=47
Reply from 98.139.180.149: bytes=32 time=230ms TTL=49
Reply from 98.139.180.149: bytes=32 time=69ms TTL=49
Reply from 98.139.180.149: bytes=32 time=81ms TTL=49
Reply from 98.139.180.149: bytes=32 time=135ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 98.139.180.149: bytes=32 time=106ms TTL=49
Reply from 98.139.180.149: bytes=32 time=397ms TTL=47
Reply from 98.139.180.149: bytes=32 time=309ms TTL=47
Reply from 98.139.180.149: bytes=32 time=280ms TTL=47
Reply from 98.139.180.149: bytes=32 time=394ms TTL=49
Reply from 98.139.180.149: bytes=32 time=517ms TTL=49
Reply from 98.139.180.149: bytes=32 time=583ms TTL=47
Reply from 98.139.180.149: bytes=32 time=405ms TTL=49
Reply from 98.139.180.149: bytes=32 time=237ms TTL=49
Reply from 98.139.180.149: bytes=32 time=111ms TTL=49
Reply from 98.139.180.149: bytes=32 time=67ms TTL=49
Request timed out.
Reply from 98.139.180.149: bytes=32 time=124ms TTL=49
Reply from 98.139.180.149: bytes=32 time=232ms TTL=49
Reply from 98.139.180.149: bytes=32 time=290ms TTL=47

Ping statistics for 98.139.180.149:
    Packets: Sent = 71, Received = 61, Lost = 10 (14% loss),
Approximate round trip times in milli-seconds:
    Minimum = 62ms, Maximum = 719ms, Average = 247ms
Control-C

colossus972

  • Newbie
  • *
  • Posts: 35
    • View Profile
Re: Internet Connection Performance
« Reply #1 on: January 22, 2012, 11:51:24 AM »
Here is log

Cable Modem
Status Signal Addresses Configuration Logs Help
This page displays detailed information intended for use by an authorized Motorola Corporation Cable Modem technician. 

--------------------------------------------------------------------------------


Time Priority Code Message
Jan 22 2012 11:42:08 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 11:16:44 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:52 3-Critical D01.0 DHCP FAILED - Discover sent, no offer received;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;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=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice  Cable Modem Reboot due to power reset ;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 11:13:51 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 09:47:15 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:24 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice  Cable Modem Reboot due to T4 timeout ;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 09:46:30 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 09:46:30 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 09:46:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 08:27:20 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:24 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice  Cable Modem Reboot due to T4 timeout ;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 08:26:27 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 08:26:27 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 08:26:26 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 07:28:50 6-Notice I502.0 Received REG-RSP while in REG-HOLD1 state;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2012 07:28:48 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e4:83:99:59:ac:9e;CMTS-MAC=64:00:f1:40:2f:60;CM-QOS=1.1;CM-VER=3.0;



--------------------------------------------------------------------------------



Status | Signal | Addresses | Configuration | Logs | Help

 
Copyright 1997-2008 

colossus972

  • Newbie
  • *
  • Posts: 35
    • View Profile
Re: Internet Connection Performance
« Reply #2 on: January 22, 2012, 11:52:34 AM »
Here is signal info:

Cable Modem
Status Signal Addresses Configuration Logs Help
This page provides information about the current upstream and downstream signal status of your Cable Modem. 

--------------------------------------------------------------------------------


Downstream  Bonding Channel Value
Channel ID 50   49   51   52   
Frequency 117000000 Hz  111000000 Hz  123000000 Hz  129000000 Hz 
Signal to Noise Ratio 35 dB  35 dB  35 dB  34 dB 
Downstream Modulation QAM256  QAM256  QAM256  QAM256 
Power LevelThe Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading 
 -3 dBmV   -2 dBmV   -4 dBmV   -5 dBmV   


Upstream  Bonding Channel Value
Channel ID 2   
Frequency 31000000 Hz 
Ranging Service ID 226 
Symbol Rate 5.120 Msym/sec 
Power Level 52 dBmV 
Upstream Modulation [6] 16QAM
 
Ranging Status  Success 


Signal Stats (Codewords) Bonding Channel Value
Channel ID 50   49   51   52   
Total Unerrored Codewords 95254500  95255009  95255157  95254761 
Total Correctable Codewords 56  14  43  0 
Total Uncorrectable Codewords 734  546  502  535 




--------------------------------------------------------------------------------



Status | Signal | Addresses | Configuration | Logs | Help

 
Copyright 1997-2008 

MediacomDrew

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 9220
    • View Profile
Re: Internet Connection Performance
« Reply #3 on: January 22, 2012, 12:59:23 PM »
Currently, I am showing higher amounts of packet loss over the last few days.  Currently, it looks like they have posted an "outage" while maintenance runs work in the area.  This could be in response to this issue, but we'll keep an eye on this and see where the levels lie when they close this.  Please keep us posted!

MediacomDrew

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 9220
    • View Profile
Re: Internet Connection Performance
« Reply #4 on: January 24, 2012, 01:01:21 PM »
I just wanted to follow up with I'm seeing now.  The outage from Sunday was cleared and I'm now seeing a pretty consistent and steady flow with no packet loss.  How have things been going since Sunday?