US Cable Support → Mediacom > Huge packet loss tonight

Re: Huge packet loss tonight

If this is a node issue the tech will be able to submit a maintenance order. I'll have more information once the appointment is completed.

the 172.30.23.53 and 12.249.240.29 servers are where im getting the packet loss and ping spikes at every time. are those servers located near my house and the tech will be working on them when he comes to my appointment?

Thank you. At this point it would be best to have a tech out to investigate. All of your signals are reporting in range. However I do show a couple of downstream signal drops.

What do you think Chad? Think its something at my end?

Here is a full 3 tracerts definitely a problem past my equipment...

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Colin>tracert 216.52.148.11

Tracing route to chicago-ts.nfoservers.com [216.52.148.11]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 6 ms 9 ms 9 ms 10.140.154.1
3 * 10 ms 7 ms 172.30.74.1
4 589 ms * 10 ms 172.30.23.53
5 1175 ms 24 ms 13 ms 12.249.240.29
6 16 ms 15 ms 16 ms cr1.cgcil.ip.att.net [12.122.99.38]
7 21 ms 14 ms 11 ms cgcil405me3.ip.att.net [12.122.99.13]
8 * * * Request timed out.
9 20 ms 13 ms 12 ms border5.po1-bbnet1.chg.pnap.net [64.94.32.10]
10 11 ms 17 ms 14 ms chicago-ts.nfoservers.com [216.52.148.11]

Trace complete.

C:\Users\Colin>tracert 216.52.148.11

Tracing route to chicago-ts.nfoservers.com [216.52.148.11]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 6 ms 7 ms 10.140.154.1
3 7 ms 7 ms 7 ms 172.30.74.1
4 1862 ms 9 ms 7 ms 172.30.23.53
5 13 ms 21 ms 14 ms 12.249.240.29
6 25 ms 15 ms 15 ms cr1.cgcil.ip.att.net [12.122.99.38]
7 13 ms 18 ms 11 ms cgcil405me3.ip.att.net [12.122.99.13]
8 * * * Request timed out.
9 * 14 ms 12 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
10 12 ms 12 ms 13 ms chicago-ts.nfoservers.com [216.52.148.11]

Trace complete.

C:\Users\Colin>tracert 216.52.148.11

Tracing route to chicago-ts.nfoservers.com [216.52.148.11]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 10.140.154.1
3 9 ms 7 ms 8 ms 172.30.74.1
4 10 ms 10 ms 8 ms 172.30.23.53
5 12 ms 12 ms 14 ms 12.249.240.29
6 1209 ms 66 ms 15 ms cr1.cgcil.ip.att.net [12.122.99.38]
7 32 ms 18 ms 11 ms cgcil405me3.ip.att.net [12.122.99.13]
8 * * * Request timed out.
9 14 ms 12 ms 83 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
10 19 ms 13 ms 13 ms chicago-ts.nfoservers.com [216.52.148.11]

Trace complete.

C:\Users\Colin>

Definitely happening at hop 5 here

1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 7 ms 7 ms 10.140.154.1
3 8 ms 8 ms 7 ms 172.30.74.1
4 7 ms 9 ms 9 ms 172.30.23.53
5 395 ms 21 ms 11 ms 12.249.240.29
6 17 ms 15 ms 16 ms cr1.cgcil.ip.att.net [12.122.99.38]
7 12 ms 12 ms 11 ms cgcil405me3.ip.att.net [12.122.99.13]
8 * * * Request timed out.
9 14 ms 14 ms 14 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
10 13 ms 14 ms 12 ms chicago-ts.nfoservers.com [216.52.148.11]

Trace complete.

Yes that information will help. More Tracerts when you're having the issue if you can. That will help us track what hop the ping spikes are happening on.

Here is another ping to google.com servers...

Trace complete.

C:\Users\Colin>ping google.com -t

Pinging google.com [74.125.225.136] with 32 bytes of data:
Reply from 74.125.225.136: bytes=32 time=26ms TTL=54
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Reply from 74.125.225.136: bytes=32 time=19ms TTL=54
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=18ms TTL=54
Reply from 74.125.225.136: bytes=32 time=19ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Reply from 74.125.225.136: bytes=32 time=24ms TTL=54
Reply from 74.125.225.136: bytes=32 time=2134ms TTL=54
Reply from 74.125.225.136: bytes=32 time=463ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=15ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=14ms TTL=54
Request timed out.
Reply from 74.125.225.136: bytes=32 time=16ms TTL=54
Request timed out.
Reply from 74.125.225.136: bytes=32 time=72ms TTL=54
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Reply from 74.125.225.136: bytes=32 time=1033ms TTL=54
Reply from 74.125.225.136: bytes=32 time=102ms TTL=54
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Request timed out.
Reply from 74.125.225.136: bytes=32 time=73ms TTL=54
Reply from 74.125.225.136: bytes=32 time=14ms TTL=54
Request timed out.
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=928ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=1799ms TTL=54
Reply from 74.125.225.136: bytes=32 time=508ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=17ms TTL=54
Request timed out.
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=64ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Reply from 74.125.225.136: bytes=32 time=15ms TTL=54
Request timed out.
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=11ms TTL=54
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=13ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.225.136: bytes=32 time=12ms TTL=54
Reply from 74.125.225.136: bytes=32 time=15ms TTL=54
Reply from 74.125.225.136: bytes=32 time=14ms TTL=54
Reply from 74.125.225.136: bytes=32 time=845ms TTL=54
Reply from 74.125.225.136: bytes=32 time=30ms TTL=54

Ping statistics for 74.125.225.136:
Packets: Sent = 66, Received = 57, Lost = 9 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 2134ms, Average = 151ms
Control-C

Is this what you needed chad? or do you need something different?

35% packet loss right now...

C:\Users\Colin>tracert 216.52.148.11

Tracing route to chicago-ts.nfoservers.com [216.52.148.11]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.140.154.1
3 8 ms 8 ms 7 ms 172.30.74.1
4 8 ms 7 ms 7 ms 172.30.23.53
5 * * * Request timed out.
6 * 15 ms 23 ms cr1.cgcil.ip.att.net [12.122.99.38]
7 12 ms 11 ms 79 ms cgcil405me3.ip.att.net [12.122.99.13]
8 * * * Request timed out.
9 30 ms 14 ms 18 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
10 12 ms 14 ms 11 ms chicago-ts.nfoservers.com [216.52.148.11]

i would like to do whatever we can do to help the issue. Here are my ping and tracerts when it happens.

C:\Users\Colin>ping 216.52.148.11 -t

Pinging 216.52.148.11 with 32 bytes of data:
Reply from 216.52.148.11: bytes=32 time=16ms TTL=54
Reply from 216.52.148.11: bytes=32 time=15ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=40ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=78ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=15ms TTL=54
Reply from 216.52.148.11: bytes=32 time=18ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=14ms TTL=54
Reply from 216.52.148.11: bytes=32 time=14ms TTL=54
Reply from 216.52.148.11: bytes=32 time=18ms TTL=54
Reply from 216.52.148.11: bytes=32 time=11ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=24ms TTL=54
Reply from 216.52.148.11: bytes=32 time=2104ms TTL=54
Reply from 216.52.148.11: bytes=32 time=463ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=14ms TTL=54
Reply from 216.52.148.11: bytes=32 time=11ms TTL=54
Reply from 216.52.148.11: bytes=32 time=14ms TTL=54
Reply from 216.52.148.11: bytes=32 time=14ms TTL=54
Reply from 216.52.148.11: bytes=32 time=23ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=15ms TTL=54
Reply from 216.52.148.11: bytes=32 time=20ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=15ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=14ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 216.52.148.11: bytes=32 time=18ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=14ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=11ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=16ms TTL=54
Reply from 216.52.148.11: bytes=32 time=22ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=11ms TTL=54
Reply from 216.52.148.11: bytes=32 time=11ms TTL=54
Reply from 216.52.148.11: bytes=32 time=22ms TTL=54
Reply from 216.52.148.11: bytes=32 time=14ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=20ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=11ms TTL=54
Reply from 216.52.148.11: bytes=32 time=13ms TTL=54
Reply from 216.52.148.11: bytes=32 time=12ms TTL=54
Reply from 216.52.148.11: bytes=32 time=11ms TTL=54
Reply from 216.52.148.11: bytes=32 time=34ms TTL=54

Ping statistics for 216.52.148.11:
Packets: Sent = 77, Received = 74, Lost = 3 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 2104ms, Average = 49ms

Well if you wouldn't like to further troubleshoot I'll go ahead and alert the area to look for it.

Its totally intermittent, good for 10-15 min then huge amount of packet loss and lose connection to the network. I brought my laptop over to my neighbors house down the road and that too has the same problem, Mediacom internet...

I've gone ahead and run 200 pings over to your modem and all of them returned fine. I do not see any signal issues either. In order to continue troubleshooting we'll probably want to run some pings and tracerts from the command line.

So I have already set an appointment for monday with a tech however I dont believe it is a problem with my equipment. All day and late last night I was great! no packet loss no lag in game. Now all of a sudden as of 5pm huge 20% packet loss. What is going on.... Cant even stay connected.