Forum Discussion

KrazeeeCOX's avatar
KrazeeeCOX
New Contributor
12 months ago

Slow trace route w/time outs

Greetings. I'm running in to an issue recently where my connection to World of Warcraft West coast servers is suddenly 3 to 5 times slower than previous. I used to experience about 50ms ping but it h...
tracert
  • WiderMouthOpen's avatar
    WiderMouthOpen
    12 months ago

    A possible workaround could be to use a VPN. I know Cox had something called "Gamer Elite" which was a rebranding of WTFast but it got discontinued. Do either of you happen to have it grandfathered in? Also, maybe another VPN might help? If it still occurs with the VPN then you pretty much know it's not a Cox issue however it is strange to see 2 people with similar problems. Are both of you West Coast?

    ::edit:: Just for comparison, I did a tracert on my FIOS connection. Seems to be routing differently. I am in RI. Notice the time outs, which are normal but the latency seems what it should be.

    Tracing route to 137.221.105.2 over a maximum of 30 hops

      1    <1 ms    <1 ms    <1 ms  RT-AX86U-22F8 [192.168.50.1]
      2     4 ms     3 ms     3 ms  lo0-100.PRVDRI-VFTTP-304.verizon-gni.net [100.40.77.1]
      3     9 ms     7 ms     7 ms  B3304.PRVDRI-LCR-22.verizon-gni.net [100.41.129.52]
      4     *        *        *     Request timed out.
      5    26 ms    14 ms     8 ms  0.ae2.GW1.BOS30.ALTER.NET [140.222.3.69]
      6     *        *        *     Request timed out.
      7     *        *       32 ms  ae2.3608.ear7.Chicago2.level3.net [4.69.142.178]
      8    31 ms    29 ms    29 ms  BLIZZARD-EN.ear7.Chicago2.Level3.net [4.7.196.134]
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11    69 ms    69 ms    70 ms  et-0-0-0-pe01-swlv10.as57976.net [137.221.83.81]
     12    75 ms    74 ms    74 ms  137.221.105.2

    Trace complete.

tjd269's avatar
tjd269
New Contributor II

Hi there, I am experiencing the exact same issue. I have been using the same service for 12 months without issue until last night... I have seemingly the same routing issues.

Ironically, a reset of the modem did fix it for one of my servers, but many other servers I would normally get sub-10 ping to, I am getting 150. Chicago also seems to be bad for me too. The LA routing seems to be really bad considering I'm in Las Vegas and should be getting literally like 8 ping or so like I usually do. Not sure where you're located though.

Some servers still work totally fine though. I am experiencing this on Counter strike and it's incredibly frustrating. I haven't found anything online except just your post. Hoping others can chime in since it doesn't show a service outage or anything either.

WiderMouthOpen's avatar
WiderMouthOpen
Esteemed Contributor
12 months ago

A possible workaround could be to use a VPN. I know Cox had something called "Gamer Elite" which was a rebranding of WTFast but it got discontinued. Do either of you happen to have it grandfathered in? Also, maybe another VPN might help? If it still occurs with the VPN then you pretty much know it's not a Cox issue however it is strange to see 2 people with similar problems. Are both of you West Coast?

::edit:: Just for comparison, I did a tracert on my FIOS connection. Seems to be routing differently. I am in RI. Notice the time outs, which are normal but the latency seems what it should be.

Tracing route to 137.221.105.2 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  RT-AX86U-22F8 [192.168.50.1]
  2     4 ms     3 ms     3 ms  lo0-100.PRVDRI-VFTTP-304.verizon-gni.net [100.40.77.1]
  3     9 ms     7 ms     7 ms  B3304.PRVDRI-LCR-22.verizon-gni.net [100.41.129.52]
  4     *        *        *     Request timed out.
  5    26 ms    14 ms     8 ms  0.ae2.GW1.BOS30.ALTER.NET [140.222.3.69]
  6     *        *        *     Request timed out.
  7     *        *       32 ms  ae2.3608.ear7.Chicago2.level3.net [4.69.142.178]
  8    31 ms    29 ms    29 ms  BLIZZARD-EN.ear7.Chicago2.Level3.net [4.7.196.134]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    69 ms    69 ms    70 ms  et-0-0-0-pe01-swlv10.as57976.net [137.221.83.81]
 12    75 ms    74 ms    74 ms  137.221.105.2

Trace complete.

  • tjd269's avatar
    tjd269
    New Contributor II
    12 months ago

    I'm west coast/Las Vegas, I figured trying a VPN would be a solid idea. Let me see...

    VPN completely fixes it. The servers I'm having issues with, and even Youtube.com, now don't have crazy latency. Same server as I trace routed above, but with a VPN:

    Tracing route to arryn.dathost.net [169.150.249.131]
    over a maximum of 30 hops:

      1    15 ms    16 ms    13 ms  100.64.1.131
      2    17 ms    16 ms    16 ms  vlan24.as04.lax1.us.m247.ro [185.236.200.17]
      3    26 ms    32 ms    32 ms  irb-2902.agg2.lax1.us.m247.ro [82.102.29.100]
      4    18 ms    24 ms    17 ms  be-2-3902.bb1n.lax1.us.m247.ro [82.102.29.112]
      5    17 ms    26 ms    15 ms  lax-b23-link.ip.twelve99.net [213.155.129.10]
      6    16 ms    17 ms    15 ms  lax-b22-link.ip.twelve99.net [62.115.143.39]
      7    40 ms    16 ms    14 ms  datacamp-ic-382478.ip.twelve99-cust.net [62.115.52.50]
      8    16 ms    16 ms    15 ms  vl222.lax-cs2-dist-1.cdn77.com [138.199.0.89]
      9    16 ms    15 ms    15 ms  arryn.dathost.net [169.150.249.131]

    Issue is completely gone on a VPN. Gotta be Cox right? Nothing on my end has changed in the past 12 months.

    • tjd269's avatar
      tjd269
      New Contributor II
      12 months ago

      I want to further add to this as it seems to only happen when routed by the cox server: langbprj01-ae2.rd.la.cox.net

      This is shown in my above post, but just to make it easy to read: 

      Tracing route to arryn.dathost.net [169.150.249.131]
      over a maximum of 30 hops:

        1     3 ms     1 ms     1 ms  192.168.0.1
        2    12 ms    12 ms    11 ms  10.73.96.1
        3     7 ms    11 ms    11 ms  100.127.5.192
        4    13 ms    10 ms    12 ms  100.120.102.36
        5   141 ms   153 ms   177 ms  langbprj01-ae2.rd.la.cox.net [68.1.4.252]
        6   175 ms   160 ms   158 ms  cox-lax.cdn77.com [169.150.195.52]
        7   133 ms   130 ms   134 ms  vl211.lax-cs2-core-1.cdn77.com [138.199.0.104]
        8   114 ms   114 ms   114 ms  vl223.lax-cs2-dist-2.cdn77.com [138.199.0.91]
        9   176 ms   180 ms   176 ms  arryn.dathost.net [169.150.249.131]


      Many servers for me are totally fine, and upon researching for a variable between this and the poor-ping servers is the cox routing server it uses. For example, this is a Dallas counter strike server, and notice the 5th jump seems to use a different Cox routing server:

      Tracing route to ullhor.dathost.net [121.127.40.169]
      over a maximum of 30 hops:

        1     3 ms     1 ms     1 ms  192.168.0.1
        2    14 ms    11 ms     9 ms  10.73.96.1
        3    13 ms    12 ms    11 ms  100.127.5.192
        4    12 ms    11 ms    11 ms  100.120.102.36
        5    44 ms    43 ms    44 ms  dalsbprj02-ae2.rd.dl.cox.net [68.1.2.121]
        6    47 ms    45 ms    45 ms  cox-dal.cdn77.com [37.19.192.28]
        7    46 ms    44 ms    44 ms  vl202.dal-clg3-dist-1.cdn77.com [185.156.45.73]
        8    51 ms    47 ms    44 ms  ullhor.dathost.net [121.127.40.169]

      Notice the dalsbprj02-ae2.rd.dl.cox.net server does not have this problem.

      COX PLEASE FIX THIS, IT MAKES THE INTERNET HORRIBLE TO USE