Forum Discussion

steve924's avatar
steve924
New Contributor
12 years ago

Packet routing issue

Just had Cox HSI based out of Las Vegas installed a month ago and service has been acceptable. I use it for general browsing, gaming and streaming media. I've been noticing a higher latency than I would consider normal for certain west coast gaming servers I connect to.

Tracing route to jennyfur.pelican.org [76.74.236.91]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  cmxp.lv.cox.net [192.168.2.1]
  2     8 ms     9 ms     8 ms  10.80.0.1
  3     9 ms    11 ms     7 ms  24-234-16-221.ptp.lvcm.net [24.234.16.221]
  4    13 ms    10 ms    10 ms  24-234-6-125.ptp.lvcm.net [24.234.6.125]
  5    15 ms     8 ms    12 ms  24-234-6-254.ptp.lvcm.net [24.234.6.254]
  6     *       39 ms    44 ms  68.1.5.140
  7    40 ms    45 ms    40 ms  10ge.ten1-3.dal-eqx-cor-1.peer1.net [206.223.118.30]
  8    55 ms    54 ms    61 ms  10ge.ten1-2.la-600w-cor-2.peer1.net [216.187.124.121]
  9    55 ms    61 ms    55 ms  10ge.xe-0-3-0.lax-600w-sbcor-2.peer1.net [216.187.88.46]
 10    73 ms    48 ms    53 ms  10ge.xe-0-0-2.lax-600w-sbdis-1.peer1.net [216.187.88.138]
 11    54 ms    47 ms    48 ms  jennyfur.pelican.org [76.74.236.91]

Trace complete.

Mind you, that server is located in Los Angeles, CA. I'm in Las Vegas, NV. My packets seem to be going from NV to AZ to TX and THEN to CA. Seems a little too roundabout.

Here's a link to someone with the same issue:

http://www.dslreports.com/forum/remark,27847498

"Cox is handing off to Peer1 in Dallas equinix for me, then back to LA. That would mean Peer1 has proper routes to cox, but cox's outbound to them is messed up."

How can this be resolved?

2 Replies

Sort By
Replies have been turned off for this discussion
  • ruledby's avatar
    ruledby
    New Contributor
    12 years ago

    Hello, I too have been having issues with latency anytime I upload a file larger than say 13mbs.  Have you noticed this at all?

    traceroute: Warning: google.com has multiple addresses; using 74.125.224.195
    traceroute to google.com (74.125.224.195), 64 hops max, 52 byte packets
    1 10.0.1.1 (10.0.1.1) 0.929 ms 0.809 ms 0.634 ms
    2 10.80.0.1 (10.80.0.1) 229.821 ms 240.468 ms 250.326 ms
    3 24-234-16-217.ptp.lvcm.net (24.234.16.217) 256.135 ms 252.912 ms 263.657 ms
    4 24-234-6-121.ptp.lvcm.net (24.234.6.121) 262.317 ms
    24-234-6-129.ptp.lvcm.net (24.234.6.129) 280.420 ms 291.651 ms
    5 24-234-6-250.ptp.lvcm.net (24.234.6.250) 290.505 ms 297.284 ms
    24-234-6-218.ptp.lvcm.net (24.234.6.218) 296.946 ms
    6 langbprj01-ae1.rd.la.cox.net (68.1.1.13) 321.636 ms 330.375 ms 333.126 ms
    7 langbbrj01-ge050000804.r2.la.cox.net (68.105.30.181) 336.150 ms 354.097 ms 357.332 ms
    8 64.233.174.238 (64.233.174.238) 157.330 ms 167.476 ms 179.493 ms
    9 72.14.236.13 (72.14.236.13) 165.737 ms 181.065 ms 188.391 ms
    10 lax02s02-in-f3.1e100.net (74.125.224.195) 198.196 ms 198.353 ms 220.189 ms

    Whenever I stop the upload, it instantly drops down to a reasonable ~23ms.  The issue is always with 10.80.0.1, but I have not been able to find why exactly I'm connecting to it, I've had two different modems (different brands), and both connect to it, so I don't believe its an internal router (I have phone with my internet); and google searches don't bring up much.

  • DerrickW's avatar
    DerrickW
    Valued Contributor
    12 years ago

    HI Steve924,

    This is an issue that we can definitely take a look at, but we would need some more information.  We would need to have you run a trace route to 2 different sites/IP addresses then we would be able to compare that information to see if the same thing occurs on those trace route results as well.   This will help determine if it is a problem on our network side or not.  Also, when you run the traceroute, could you bypass your router and connect the modem directly to the computer.  If you like you can post the information here, or you can email it to me and my team at coxhelp@cox.com and we will be more than happy to take a look at that for you.