dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
49
share rss forum feed

deisdestiny

join:2013-01-17
Columbus, OH
reply to jjohnso1

Re: Intermittent packet loss Columbus OH area

Could I ask those of us that are experiencing the intermittent extreme packet loss to do a few traceroutes to common servers out there such as google and report their hops here?

Like so:

Tracing route to google.com [74.125.228.67]
over a maximum of 30 hops:

1 * * * Request timed out.
2 10 ms 9 ms 8 ms 10.35.25.94
3 12 ms 12 ms 8 ms 10.35.24.1
4 8 ms 11 ms 8 ms 10.35.11.13
5 24 ms 23 ms 26 ms eqixva-google-gige.google.com [206.126.236.21]
6 23 ms 25 ms 31 ms 209.85.252.46
7 29 ms 36 ms 26 ms 72.14.238.247
8 32 ms 26 ms 26 ms iad23s07-in-f3.1e100.net [74.125.228.67]
I ask as I am trying to find the common servers we are hopping through. The #2 hop for me is always the same, but after that they can vary depending on load as expected. If we can start drilling this down we can at least start eliminating possibilities for the packet loss. There are a large number of things that could be causing this packet loss, but we could be looking at either a bad server at one of the common hops, or an infrequently used load balancing server that is failing.

SmokePing is a good test to determine if there is a problem, but it unfortunately gives little helpful information other than time of day. We are going to need to run packet loss tests from our individual residences and/or have the techs at WOW run tests to each of their servers and monitor the loss over a few days.

Sock

join:2011-08-13
Columbus, OH

Here's one example from back in December when I was trying to troubleshoot. I'll grab a current one when the issue occurs tomorrow morning.

Hops Loss IP Name Location Tzone Avg Min Max Network
0 0 192.168.0.111 GOLDENMONKEY - - 0.0 0 0 [Local Network]
1 0 192.168.0.254 DD-WRT - - 0.0 0 0 [Local Network]
2 0 172.27.35.1 - - - 1.0 1 1 [Local Network]
3 100 - - - - - - - -
4 0 10.35.25.38 - - - 1090.0 416 1353 [Local Network]
5 0 10.35.11.13 - - - 1048.0 347 1332 [Local Network]
6 100 - - - - - - - -
7 0 209.85.252.80 - Mountain View, usa - 1049.0 274 1331 Google Inc.
8 7 72.14.236.152 - Mountain View, usa - 1053.0 711 1352 Google Inc.
8 7 72.14.236.146 - Mountain View, usa - 1024.0 788 1340 Google Inc.
9 6 209.85.241.222 - Mountain View, usa - 997.0 628 1396 Google Inc.
9 6 209.85.243.114 - Mountain View, usa - 956.0 737 1416 Google Inc.
10 3 216.239.48.59 - Mountain View, usa - 788.0 436 1213 Google Inc.
10 3 216.239.48.159 - Mountain View, usa - 610.0 195 868 Google Inc.
10 3 216.239.48.183 - Mountain View, usa - 805.0 289 1213 Google Inc.
10 3 216.239.48.157 - Mountain View, usa - 1007.0 483 1386 Google Inc.
11 100 - - - - - - - -
12 12 173.194.75.99 www.google.com Mountain View, usa - 965.0 390 1386 Google Inc.


Sock

join:2011-08-13
Columbus, OH
reply to deisdestiny

Here's a trace from this morning's incident:

Target Name: www.google.com
IP: 173.194.75.103
Date/Time: 2/7/2013 8:41:50 AM to 2/7/2013 8:42:09 AM

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 20 0 0.0 0 4 0 DD-WRT [192.168.0.254]
2 18 18 100.0 0 0 0 [-]
3 20 4 20.0 11 1247 258 [10.35.25.46]
4 20 1 5.0 12 2135 430 [10.35.11.33]
5 20 1 5.0 24 1230 371 eqixva-google-gige.google.com [206.126.236.21]
6 20 2 10.0 24 1143 321 [209.85.252.46]
7 17 5 29.4 25 746 232 [72.14.236.98]
8 17 3 17.6 39 1719 559 [209.85.243.114]
9 10 0 0.0 37 795 261 [216.239.48.159]
10 18 18 100.0 0 0 0 [-]
11 20 6 30.0 37 1160 214 ve-in-f103.1e100.net [173.194.75.103]


deisdestiny

join:2013-01-17
Columbus, OH

So I have uncovered a bit more information in my tests. Hopefully this information gets passed on to the appropriate people at WOW.

I have been monitoring connectivity with pings to the following WOW servers/routes "10.35.25.94" and "10.35.24.2". When the disconnects occur I am still able to continue pinging those servers with NO interruption.

So, this should indicate that the issue is beyond those links in the chain.

Continuing to dive into the rabbit hole...