Ran the traceroute tool in the launcher - and found what appears to be my connectivity issue.
An amazon node in Virginia - please run the tool and see if your packets die at this same address as mine do.
My problem seems to be Amazon’s network , are you guys getting the same?
Yes, the traceroute tool reports the same thing for me. Intriguing.
I get multiple timeouts before finally reaching 188.8.131.52, which is an Amazon server in Seattle.
Just obtained a different result from a buddy further up north
But guess whose it is and where it is?
Amazon node, Virginia Beach Virginia - same as the 99.82 address!
yep, i got 184.108.40.206 which is Amazon…
Can someone describe whether they are timing out during the traceroute but eventually reaching the destination IP, or if the traceroute fails?
What is happening for me is I am timing out 7 times before finally completing the traceroute. That is always an Amazon server in Seattle, though, not Virginia.
I’m in Chicago, so I’m not entirely sure why my traceroute would go through Seattle on its way to London, which is where I believe TQ is located.
I am fallout out after the 10th ping or whatever it is, and it just continues with request timeouts
Mine predictably times out on the 11th through 17th request and then always, always completes on the 18th request. Strange.
I’m guessing your hops can get about the same time going either way. My traceroute packets just get fed into a dead end. Is your connectivity really spotty? I can’t even play… I can connect most of the time, but as soon as I want to connect to the server that runs grids for the system its gg hope my pod will survive floating out of the undock and into a bunch of trigs as the screen stops loading or goes black
Daedalus - if you do a search for ‘whois (ip address)’ for the last good hop, no parentheses - do you get an amazon node?
I’m guessing Amazon had to roll back their DNS to a ‘safe config’ and now if they are a single point of failure, we can’t really get a decent connection
Here’s the first one to time out for me:
NetRange: 220.127.116.11 - 18.104.22.168
Organization: Amazon Technologies Inc. (AT-88-Z)
Here is a good article about why traceroute makes things that aren’t an issue look like an issue.
The long and the short of it is the “Request timed out” messages are likely not telling you what you think they are telling you. Most likely they are telling you that the host that is “timing out” in the chain is likely blocking ping/icmp (echo) requests.
Hello, from Italy here.
In last 5months i played regularly everyday without problems, only some randoms dc by time to time that costed me 1b+…
Today for the first time i can see how many people are playing in launcher but i can’t play when i try to connect to the game… here is my tracert from eve launcher
" Starting traceroute diagnostics - this may take several minutes
Starting tracert for launcher.eveonline.com
Traccia instradamento verso d1hoqe10mv32pv.cloudfront.net [22.214.171.124]
su un massimo di 30 punti di passaggio:
1 3 ms 1 ms <1 ms 192.168.1.1
2 * * * Richiesta scaduta.
3 23 ms 22 ms 23 ms 172.17.192.212
4 110 ms 28 ms 60 ms 172.17.193.50
5 28 ms 29 ms 28 ms 172.19.184.40
6 33 ms 33 ms 33 ms 172.19.177.18
7 * * 54 ms etrunk49.milano50.mil.seabone.net [126.96.36.199]
8 48 ms 47 ms 47 ms ae20.franco32.fra.seabone.net [188.8.131.52]
9 46 ms 45 ms 61 ms amazon.franco32.fra.seabone.net [184.108.40.206]
10 * * * Richiesta scaduta.
11 48 ms 48 ms 48 ms 220.127.116.11
12 * * * Richiesta scaduta.
13 * * * Richiesta scaduta.
14 * * * Richiesta scaduta.
15 * * * Richiesta scaduta.
16 * * * Richiesta scaduta.
17 45 ms 45 ms 45 ms server-13-35-253-9.fra6.r.cloudfront.net [18.104.22.168]
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.