dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
633
share rss forum feed

paracyst

join:2009-06-01
Macon, GA

1 edit

[GA] Middle GA routing issues, someone from Cox please help!

I posted this in the general Cox section, but I figured I'd post it here in the middle GA section to see if anyone else is having these problems. If you could, could any middle GA people also post traceroutes to the ips below? If I can read this right, and based on some more traces today, it looks like there is a problem with one of Cox's Atlanta routers

Original post:
For the past few days, my pings have jumped roughly 30-60 ms to most sites. This is incredibly annoying since I do a lot of online gaming and I'm now receiving pings that are 2x higher on some gameservers than usual. I'm in Macon, GA. Could someone at Cox please let me know what's going on?

For example, below I've included traceroutes to various servers in Atlanta. But note: this problem happens on servers located all over the country, not just Atlanta. I normally would receive response times of 10ms to 20ms to these, but notice how I now receive pings of 60-70+:

over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1] 
  2     7 ms     7 ms    12 ms  10.0.48.1 
  3     9 ms    18 ms    11 ms  68.1.8.49 
  4    11 ms    19 ms    12 ms  macnhdrj02-xe030.0.rd.mc.cox.net [68.1.8.69] 
  5    48 ms    51 ms    43 ms  68.1.2.109 
  6    65 ms    49 ms    54 ms  xe1-0.cr01.dfw01.mzima.net [206.223.118.62] 
  7    67 ms    67 ms    72 ms  te1-1.cr1.atl1.us.packetexchange.net [69.174.120.50] 
  8    82 ms    74 ms    75 ms  67.199.136.194 
  9    64 ms    64 ms    69 ms  70.32.42.18.rdns.ubiquityservers.com [70.32.42.18] 
 
Trace complete.
 
Tracing route to 69.12.54.12 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1] 
  2     8 ms    10 ms     7 ms  10.0.48.1 
  3    11 ms    11 ms     9 ms  68.1.8.49 
  4    10 ms     9 ms    10 ms  macnhdrj02-xe030.0.rd.mc.cox.net [68.1.8.69] 
  5    44 ms    49 ms    47 ms  68.1.2.109 
  6    64 ms    69 ms    66 ms  equinix-dal.megapath.net [206.223.118.33] 
  7    68 ms    65 ms    65 ms  ae0-0.dllstx97-mxc2.bb.megapath.net [155.229.57.74] 
  8    65 ms    66 ms    71 ms  ae3-0.atlngamq-mxc2.bb.megapath.net [155.229.57.166] 
  9    77 ms   104 ms   100 ms  ge-2-1-0-0.c00.atp.bb.megapath.net [155.229.101.194] 
 10    75 ms    65 ms    73 ms  ge0-3.a20.atp.bb.megapath.net [155.229.101.30] 
 11    81 ms    67 ms    67 ms  69.12.54.12 
 
Trace complete.
 
Tracing route to v-64-94-238-63.unman-vds.internap-atlanta.nfoservers.com [64.94.238.63]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1] 
  2    10 ms     7 ms    10 ms  10.0.48.1 
  3     9 ms    15 ms     9 ms  68.1.8.1 
  4     9 ms     9 ms    10 ms  macnhdrj01-xe030.0.rd.mc.cox.net [68.1.8.65] 
  5    43 ms    50 ms    45 ms  68.1.2.109 
  6    46 ms    43 ms    46 ms  gigabitethernet2-12.ar5.GRU1.gblx.net [64.209.94.93] 
  7    79 ms    83 ms    78 ms  po2.ar5.ATL1.gblx.net [67.17.105.218] 
  8    73 ms    64 ms    68 ms  Internap-Atlanta.TenGigabitEthernet3-4.ar5.ATL1.gblx.net [207.218.80.218] 
  9    70 ms    62 ms    64 ms  border10.tge3-1-bbnet1.acs.pnap.net [64.94.0.12] 
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 
 Tracing route to atle301.multiplay.co.uk [206.217.143.101]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1] 
  2    13 ms    11 ms    13 ms  10.0.48.1 
  3    85 ms   213 ms   227 ms  68.1.8.1 
  4    12 ms     9 ms    10 ms  macnhdrj01-xe030.0.rd.mc.cox.net [68.1.8.65] 
  5    44 ms    51 ms    43 ms  68.1.2.121 
  6    47 ms    48 ms    48 ms  70.167.150.130 
  7    44 ms    43 ms    43 ms  ae0-50g.cr1.dfw1.us.nlayer.net [69.31.63.125] 
  8    51 ms    49 ms    54 ms  xe-1-1-0.cr1.iah1.us.nlayer.net [69.22.142.2] 
  9    95 ms    66 ms    71 ms  xe-4-2-1.cr1.atl1.us.nlayer.net [69.22.142.118] 
 10    65 ms    65 ms    75 ms  as36352.xe-4-0-1-107.cr1.atl1.us.nlayer.net [69.31.135.94] 
 11    76 ms    68 ms    66 ms  atle301.multiplay.co.uk [206.217.143.101] 
 
Trace complete.
 
Tracing route to tlweb.gtm.gatech.edu [130.207.244.120]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1] 
  2     9 ms    16 ms     7 ms  10.0.48.1 
  3    18 ms    11 ms     9 ms  68.1.8.1 
  4    12 ms     9 ms    11 ms  macnhdrj01-xe030.0.rd.mc.cox.net [68.1.8.65] 
  5    65 ms    64 ms    64 ms  maribprj01-ae1.0.rd.at.cox.net [68.1.0.41] 
  6    68 ms    68 ms    68 ms  sox-to-rich-gw2.sox.net [143.215.194.6] 
  7    65 ms    66 ms    68 ms  campus2-rtr.gatech.edu [130.207.254.187] 
  8   131 ms    70 ms    74 ms  rich-rtr.gatech.edu [130.207.254.38] 
  9    65 ms    66 ms    67 ms  tlweb.rich.gatech.edu [130.207.244.120] 
 
Trace complete.
 

I would appreciate it if someone at Cox could look into the problem and let me know what's going on. Thank you


Irish Shark
Play Like A Champion Today
Premium,MVM
join:2000-07-29
Las Vegas, NV
kudos:5

1 edit

In your first tracert at the third hop, I get this:

PING 68.1.8.49 (68.1.8.49): 56 data bytes
64 bytes from 68.1.8.49: icmp_seq=0 ttl=246 time=85.821 ms
Request timeout for icmp_seq 1
64 bytes from 68.1.8.49: icmp_seq=2 ttl=246 time=80.055 ms
64 bytes from 68.1.8.49: icmp_seq=3 ttl=246 time=82.245 ms
64 bytes from 68.1.8.49: icmp_seq=4 ttl=246 time=79.261 ms
64 bytes from 68.1.8.49: icmp_seq=5 ttl=246 time=78.361 ms
64 bytes from 68.1.8.49: icmp_seq=6 ttl=246 time=78.674 ms
64 bytes from 68.1.8.49: icmp_seq=7 ttl=246 time=79.530 ms
64 bytes from 68.1.8.49: icmp_seq=8 ttl=246 time=78.647 ms
64 bytes from 68.1.8.49: icmp_seq=9 ttl=246 time=89.844 ms

--- 68.1.8.49 ping statistics ---
10 packets transmitted, 9 packets received, 10.0% packet loss
round-trip min/avg/max/stddev = 78.361/81.382/89.844/3.737 ms

EDIT: Tracert

Traceroute has started…

traceroute to 68.1.8.49 (68.1.8.49), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 3.446 ms 0.827 ms 0.772 ms
2 * * *
3 24-234-16-121.ptp.lvcm.net (24.234.16.121) 7.384 ms 9.052 ms 8.243 ms
4 24-234-6-33.ptp.lvcm.net (24.234.6.33) 8.206 ms 9.880 ms 8.143 ms
5 68.1.4.158 (68.1.4.158) 77.629 ms 78.811 ms 77.692 ms
6 lkhnbasi01.rd.at.cox.net (68.1.8.9) 82.809 ms 79.959 ms 81.354 ms
7 68.1.8.49 (68.1.8.49) 107.548 ms 86.333 ms 81.458 ms

--
"You can observe a lot by watching". Yogi Berra


paracyst

join:2009-06-01
Macon, GA
reply to paracyst

I should also mention that I've run the same tracerts / done the same pings from another computer on the complete opposite side of town and the results were the same -- I wanted to rule out any problems on my end. My speeds are perfect as well, it's just this ping issue that is messing up an otherwise great connection


FrankP999

join:2009-07-06
Macon, GA

I am having slow connections and the same ping problems. It started about mid-May. I have Cox Premium. Ping times to Atlanta sites are in the 70 range when I formerly got 17-20 even on an iPad wifi. Connect speed should be 28 and I am regularly getting 18-22.


paracyst

join:2009-06-01
Macon, GA

2 edits

Exactly. I contacted CoxTech1 on here, but apparently 70-90ms pings to a location an hour away is "reasonable" (even though it's been 10-20ms for the past decade) so I would not expect resolution of this issue anytime soon. It simply doesn't make sense that pings would virtually triple like this. The games I play need 10-60 ping for the optimal experience.

This whole situation is puzzling since this has basically never happened in the 10 years I've been with Cox. If anything, in recent years my pings to Texas based servers have gotten better, rather than worse like I'm seeing with virtually every other location now.

I'd imagine your pings are pretty crappy to other east coast locations as well? I've gone from 30 ms to Virginia to 90 ms.


paracyst

join:2009-06-01
Macon, GA
reply to paracyst

Okay, this thread can now be closed... I personally emailed Cox's NOC engineers and had my pings fixed in literally 10 minutes at 2:30 in the morning. Great service there. It really does pay to deal with the higher-ups who know what they're doing



Irish Shark
Play Like A Champion Today
Premium,MVM
join:2000-07-29
Las Vegas, NV
kudos:5

What was the fix?