http://www.dslreports.com/forum/GA-Maddening-intermittent-packet-loss-27159382 en Wed, 22 May 2013 01:35:25 EDT Wed, 22 May 2013 01:35:25 EDT http://www.dslreports.com/forum/Re-GA-Maddening-intermittent-packet-loss-27159859 http://www.dslreports.com/forum/Re-GA-Maddening-intermittent-packet-loss-27159859 Sat, 19 May 2012 09:49:17 EDT http://www.dslreports.com/forum/Re-GA-Maddening-intermittent-packet-loss-27159458 http://www.dslreports.com/forum/Re-GA-Maddening-intermittent-packet-loss-27159458 Sat, 19 May 2012 00:41:24 EDT http://www.dslreports.com/forum/GA-Maddening-intermittent-packet-loss-27159382
I must say the same thing is happening that caused me to leave in the first place. Random intermittent packet loss.

ping www.google.com -n 1000

...

Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Reply from 173.194.37.83: bytes=32 time=14ms TTL=52
Reply from 173.194.37.83: bytes=32 time=19ms TTL=52
Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Reply from 173.194.37.83: bytes=32 time=13ms TTL=52
Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.194.37.83: bytes=32 time=2534ms TTL=52
Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Reply from 173.194.37.83: bytes=32 time=14ms TTL=52
Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Reply from 173.194.37.83: bytes=32 time=14ms TTL=52
Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Reply from 173.194.37.83: bytes=32 time=14ms TTL=52
Reply from 173.194.37.83: bytes=32 time=16ms TTL=52
Reply from 173.194.37.83: bytes=32 time=16ms TTL=52
Reply from 173.194.37.83: bytes=32 time=16ms TTL=52
Reply from 173.194.37.83: bytes=32 time=16ms TTL=52
Reply from 173.194.37.83: bytes=32 time=17ms TTL=52
Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Reply from 173.194.37.83: bytes=32 time=17ms TTL=52
Reply from 173.194.37.83: bytes=32 time=14ms TTL=52
Reply from 173.194.37.83: bytes=32 time=16ms TTL=52
Reply from 173.194.37.83: bytes=32 time=14ms TTL=52
Reply from 173.194.37.83: bytes=32 time=17ms TTL=52
Reply from 173.194.37.83: bytes=32 time=17ms TTL=52
Reply from 173.194.37.83: bytes=32 time=15ms TTL=52
Reply from 173.194.37.83: bytes=32 time=14ms TTL=52
Reply from 173.194.37.83: bytes=32 time=17ms TTL=52
Reply from 173.194.37.83: bytes=32 time=16ms TTL=52
Reply from 173.194.37.83: bytes=32 time=16ms TTL=52
Reply from 173.194.37.83: bytes=32 time=14ms TTL=52
Reply from 173.194.37.83: bytes=32 time=17ms TTL=52

Ping statistics for 173.194.37.83:
Packets: Sent = 582, Received = 574, Lost = 8 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 2534ms, Average = 19ms
Control-C
^C

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

Tracing route to www.l.google.com [173.194.37.83]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms xxx.xxx.xxx.xxx
2 6 ms 6 ms 7 ms xxx.xxx.xxx.xxx
3 9 ms 9 ms 9 ms xxx.xxx.xxx.xxx
4 8 ms 10 ms 9 ms 172.30.31.70
5 9 ms 9 ms 9 ms 172.30.31.73
6 15 ms 15 ms 15 ms 12.215.0.26
7 18 ms 16 ms 18 ms cr84.attga.ip.att.net [12.122.140.62]
8 16 ms 19 ms 15 ms cr2.attga.ip.att.net [12.123.22.249]
9 15 ms 13 ms 15 ms 12.122.140.213
10 17 ms 14 ms 15 ms 12.249.190.14
11 15 ms 16 ms 15 ms 72.14.239.100
12 16 ms 16 ms 15 ms 64.233.175.94
13 15 ms 15 ms 13 ms atl14s08-in-f19.1e100.net [173.194.37.83]

Trace complete.

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

Tech came out 3 years ago and dug new line from pole, replaced equipment on pole, etc. but I ended up leaving due to the fact that it never got fixed.

Recently a tech came out (who was awesome BTW.... props Daryl) and replaced some more stuff (old mediacom amp and splitter that he says was supposed to be replaced by the last tech). We thought we had it fixed but within 24h it had returned.

Valdosta, GA has a history of poor interntet service (especially after a flood a few years ago), but Mediacom moved their NOC to a whole new location and was supposed to have fixed all of these problems.

Help if any higher ups get this, I watched as the tech checked everything from the pole to my modem, and I really think that this is a problem a little further upstream.

I worked for an ISP for 3 years and know quite a bit about stuff at Layer 3, and have a little knowledge about Layer 1 and 2 as well.

For all it's other problems w/r/t oversubscription of nodes and underdelivery of their promised information rate, AT&T never seemed to have significant packet loss.]]> http://www.dslreports.com/forum/GA-Maddening-intermittent-packet-loss-27159382 Fri, 18 May 2012 23:52:00 EDT