These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
Previous page123
 

Crippling Slow Speeds Login
Author
Previous Topic Next Topic
Budrick3
Moira.
#41 - 2015-09-07 23:58:45 UTC
Quote:
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.


I saw that the ping shot up to 235 on 67.16.141.137 which so happens to be the same "Lvl 3 communications" http://ipv4.mobi/ip/po3-20G.ar6.LON3.gblx.net.html .

I then used another ping testing website which unfortunately did not give me the ip, but it avged to Europe to be 130. I then did a ping / packet test straight to 67.16.141.137 and this is what I got.

Quote:
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


0 Packet loss.
Webvan
All Kill No Skill
#42 - 2015-09-08 00:07:43 UTC
Space Overlord wrote:


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

Not a prob. For those brave enough, I'll mention it again, just go to sourceforge and search for a Traceroute program. There are a bunch of them there and really-really easy to use, and opensource so you are not getting buy me popups or malware. They all typically offer an export feature to save reports.

What a traceroute network diagnostic program will do is show every server you are connecting thru to the game server, and show their response times. This is how you find problems in connections to remote servers. In some cases, you could be connecting/hop through 30 servers, and if one goes bad, your final connection to the game server is poor or broken (not CCP's fault). It will show exactly where the problem is, and you can generate and export a report to send to your ISP tech support. Your ISP's sys admin can reroute the connection to one that works for you, or they contact the sys admin of the offending network computer to fix the issue. This isn't something CCP does, it's between you and your own ISP. It's part of what you pay your ISP for.

Just point it to the EVE website or point it at 87.237.38.200 which will trace to TQ from your location. Seems that Cox is routing you through a bad or overloaded server. I'm routing a different way from a different ISP with no issues so I can't test it myself otherwise I would. However, I did ping the offending server mentioned and it's really horrid, over 1000ms which is just total fail.

I'm in it for the money

Ctrl+Alt+Shift+F12
Space Overlord
K162 Chaos
#43 - 2015-09-08 00:29:00 UTC
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.
Chuck GreenMan
Brave Newbies Inc.
Brave Collective
#44 - 2015-09-08 00:29:09 UTC
Budrick3 wrote:
Chuck GreenMan wrote:
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 :(


What IP did you trace too?



I just used speedtest, seems it gets better later in the day. Might be local traffic?
Webvan
All Kill No Skill
#45 - 2015-09-08 00:52:21 UTC
Space Overlord wrote:
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.

Thanks Smile
Yes, that's why I keep mentioning generating a traceroute report to send to the ISP. CCP cannot technically do anything about it, unfortunately, as they don't own those servers. It's your ISP that has the greatest power to reroute your connection through working servers or have the problem server repaired. IT was my college minor, server admin and tech support (with working exp), and traceroute is a common diagnostic tool for determining network problems which this clearly is. Good luck.

I'm in it for the money

Ctrl+Alt+Shift+F12
Budrick3
Moira.
#46 - 2015-09-08 02:57:58 UTC
So I sent the following message to Cox Communications via their Technical support Email. I think it will be easier for them to fwd this to the right person instead of me babbling to some random tech on the phone. I used to work for Cox, and still have a few contacts phone #s if this does not work out. Cross your fingers boys..

Quote:
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
Space Overlord
K162 Chaos
#47 - 2015-09-08 06:26:50 UTC
Hope this works was getting so frustrated today
Webvan
All Kill No Skill
#48 - 2015-09-08 06:54:44 UTC  |  Edited by: Webvan
ugh you can't even ping the EVE servers any longer, CCP blocks it now I just checked. There is a reddit here on it. Not directly anyway, sounds like your pings are mostly failing before you even reach TQ.

However, just pinging in the general area is still doable, should not make a difference. CCP should give us an IP to ping close to them, as their WIKI is unbelievably outdated with bogus information... AS USUALXEvilPRoll

I just used this site, it's not London but it's close, just select the Coventry server they have listed in the UK (it's on that funny island thing to the left of Europe Lol ). http://www.pingtest.net/result/130444236.png <-- my result from south-west US to the UK

CCP, can you give us a server/IP to test our routs/pings with for crying out loud?!?
And update your stupid wiki, dang!


If you want an IP to traceroute, this is a London commercial datacenter from coreix.net being: 85.13.193.200
For me it's the same as the above .png image.

I'm in it for the money

Ctrl+Alt+Shift+F12
solon101
Trillium Invariant
Honorable Third Party
#49 - 2015-09-10 02:43:26 UTC  |  Edited by: solon101
Previous page123