Forum Discussion

Eineich's avatar
Eineich
New Contributor
4 years ago

Packet loss to Atlanta cox IP from Las Vegas

Hello,

For roughly the past month or so i've been experiencing intermittent packet loss on my Gigabit connection, primarily when playing games.  After running various traceroutes i've discovered this appears to be happening for 70.167.151.110 and 68.105.30.130, both of which are tied to a Cox server location in Atlanta.

Listed below are traces to both google.com and Blizzard's west coast servers.  So the main question is how do I resolve this?  I shouldn't be getting routed through Atlanta back over to California from Las Vegas.  This only started happening within the last month or so.  How can we revert this/ensure i'm not running through this path?

C:\Users\Eineich>pathping google.com

Tracing route to google.com [172.217.4.174]
over a maximum of 30 hops:
0 Eineich [192.168.0.162]
1 192.168.0.1
2 10.80.112.1
3 100.127.4.186
4 100.120.102.28
5 68.1.4.254
6 ip70-167-151-110.at.at.cox.net [70.167.151.110]
7 72.14.238.175
8 108.170.234.213
9 lax28s01-in-f174.1e100.net [172.217.4.174]

Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Eineich [192.168.0.162]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 10.80.112.1
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% 100.127.4.186
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% 100.120.102.28
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% 68.1.4.254
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% ip70-167-151-110.at.at.cox.net [70.167.151.110]
0/ 100 = 0% |
7 15ms 0/ 100 = 0% 0/ 100 = 0% 72.14.238.175
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 108.170.234.213
0/ 100 = 0% |
9 15ms 0/ 100 = 0% 0/ 100 = 0% lax28s01-in-f174.1e100.net [172.217.4.174]

Tracing route to 24.105.30.129 over a maximum of 30 hops

0 Eineich [192.168.0.162]
1 192.168.0.1
2 10.80.112.1
3 100.127.4.186
4 100.120.102.28
5 langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 68.105.30.130
7 ae1-br01-eqla1.as57976.net [137.221.68.33]
8 137.221.68.83
9 24.105.30.129

Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Eineich [192.168.0.162]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 10.80.112.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 100.127.4.186
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% 100.120.102.28
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% langbprj01-ae1.rd.la.cox.net [68.1.1.13]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 68.105.30.130
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqla1.as57976.net [137.221.68.33]
0/ 100 = 0% |
8 23ms 0/ 100 = 0% 0/ 100 = 0% 137.221.68.83
0/ 100 = 0% |
9 16ms 0/ 100 = 0% 0/ 100 = 0% 24.105.30.129

Trace complete.

4 Replies

  • JonathanJ's avatar
    JonathanJ
    Former Moderator
    @Eineich

    Showing the traces start out with a 192. meaning a router connection. If you using a stand-alone modem please bypass the router and re-run the traceroutes. Don't forget to reboot the modem after bypassing the router.

    Jonathan J
    Cox Moderator

    • Eineich's avatar
      Eineich
      New Contributor

      Hi Jonathan, any update here?  Can some sort of test be run against my current connection to see why i'm getting this packet loss and being routed through this location?

  • Eineich's avatar
    Eineich
    New Contributor

    That was already done, same results. It does not happen 100% of the time a traceroute is run, but most of the time.  I've replaced both the router and modem when this began.  This clearly shows i'm being directed to a Cox server or location in Atlanta that is dropping packets.Note 0 issues prior to exiting my network on a wired PC connection.

  • Eineich's avatar
    Eineich
    New Contributor

    So far it always runs through there, it just doesn't always drop the packets.