I have Cox Cable provider. Local servers about 20-30 ping up until i hit, po3-20G.ar6.LON3.gblx.net router then its packet loss and constantly over 170 ping

I have Cox Cable provider. Local servers about 20-30 ping up until i hit, po3-20G.ar6.LON3.gblx.net router then its packet loss and constantly over 170 ping

Clearly a net issue, what ISP do you guys have?

I have cox and am getting 60 mbs download to local servers with a low ping. When i ping UK servers i am getting a 370 ping... Spain is 170 or so.

Can someone please find a way to fix this :(

yay someone finally ran a diagnostic as recommended. That's owned by Level 3 Communications, I've had issues with them in the past. They have a number of routs to Europe, and if you send your ISP any traceroute log files, they may reroute the connection ending the problem for you.

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 8 ms 10.5.128.1
3 9 ms 10 ms 8 ms ip72-214-194-37.ga.at.cox.net [72.214.194.37]
4 51 ms 50 ms 48 ms dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 38 ms 45 ms 36 ms ae21-10G.ar7.dal2.gblx.net [64.215.187.1]
6 235 ms 203 ms 203 ms te6-4-10G.ar6.LON3.gblx.net [67.16.141.137]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Pinging 67.16.141.137 with 32 bytes of data:
Reply from 67.16.141.137: bytes=32 time=145ms TTL=248
Reply from 67.16.141.137: bytes=32 time=221ms TTL=248
Reply from 67.16.141.137: bytes=32 time=123ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=125ms TTL=248
Reply from 67.16.141.137: bytes=32 time=180ms TTL=248
Reply from 67.16.141.137: bytes=32 time=138ms TTL=248
Reply from 67.16.141.137: bytes=32 time=133ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=123ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=124ms TTL=248
Reply from 67.16.141.137: bytes=32 time=124ms TTL=248
Reply from 67.16.141.137: bytes=32 time=123ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=121ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=277ms TTL=248
Reply from 67.16.141.137: bytes=32 time=223ms TTL=248
Reply from 67.16.141.137: bytes=32 time=125ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=127ms TTL=248
Reply from 67.16.141.137: bytes=32 time=124ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=121ms TTL=248
Reply from 67.16.141.137: bytes=32 time=123ms TTL=248
Reply from 67.16.141.137: bytes=32 time=127ms TTL=248
Reply from 67.16.141.137: bytes=32 time=124ms TTL=248
Reply from 67.16.141.137: bytes=32 time=123ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=121ms TTL=248
Reply from 67.16.141.137: bytes=32 time=297ms TTL=248
Reply from 67.16.141.137: bytes=32 time=320ms TTL=248
Reply from 67.16.141.137: bytes=32 time=168ms TTL=248
Reply from 67.16.141.137: bytes=32 time=249ms TTL=248
Reply from 67.16.141.137: bytes=32 time=142ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=123ms TTL=248
Reply from 67.16.141.137: bytes=32 time=126ms TTL=248
Reply from 67.16.141.137: bytes=32 time=171ms TTL=248
Reply from 67.16.141.137: bytes=32 time=259ms TTL=248
Reply from 67.16.141.137: bytes=32 time=131ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=121ms TTL=248
Reply from 67.16.141.137: bytes=32 time=132ms TTL=248
Reply from 67.16.141.137: bytes=32 time=121ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=121ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=122ms TTL=248
Reply from 67.16.141.137: bytes=32 time=123ms TTL=248

Ping statistics for 67.16.141.137:
Packets: Sent = 54, Received = 54, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 320ms, Average = 145ms

thanks guys im not a tec guy at all.
feels like im getting the cox :-)

What IP did you trace too?

so the only way around it is to get the isp to do something about it?

im kicking this dude 100m isk for the help.

First thank you for taking the time to help. Before you read any further though, this support request more than likely will need to go to a system administrator or high level network engineer to resolve the problem.

For close to a week now, I, as well as other Cox Communication customers have been experiencing tremendous latency, and some packet loss when attempting to play a game called Eve Online which unfortunately makes the game unplayable for various reasons. All other connections and internet services run really well with the exception of this game. What makes this connection unique is that the game server is located in Europe. After rallying together with other players on the forums, we over time have found out that this problem is only occurring to Cox Communication customers.

If you are interested, Here are a few forums illustrating the commonality of Cox Customers having this problem.

https://forums.eveonline.com/default.aspx?g=posts&t=444123&p=2
https://forums.eveonline.com/default.aspx?g=posts&t=443945&p=2

One of the IPs that are being used to attempt in diagnosing the problem is 87.237.38.200, port 26000 TCP.

When running a tracert to that IP, there is a hop te6-4-10G.ar6.LON3.gblx.net [67.16.141.137] which we believe to be the offending server (extreme erratic fluctuations in pings) perhaps causing the issue which seems to be owned by "Lvl 3 communications" if I am not mistaking.

Our request is that you run some tests of your own to help verify our findings, and to contact the offending server / party to help resolve this problem. Or reroute traffic to another server to attain a better connection.

We appreciate your assistance, and are more than willing to help in anyway possible to resolve this problem. I myself used to work for Cox Communications as a technical support specialist before getting laid off due to consolidation, and though that was difficult, I still love the company! Please help an ex employee out and make several people's day!!!

Best Regards