I am able to get as far as in station with a character sometimes before, stutter, connection lost, even if another person on the network is on TQ just fine. Other times I dont even see character select and get the no server connection error. I was having a problem yesterday where I couldnt login to character because “cant have 2 alpha” but, game was closed however character said online in status. Had to relog out twice before it went offline, maybe thats why its showing 24277? cause I have been having problems staying on more than 10 min for past 3 days.
Achievement: Log into game… not unlocked
I don’t understand that either, my brother who lives 2 kilometers away can log in, I can’t
Their networks are just set up in a way where traceroute fails to show us meaningful results.
I wouldn’t read too much into it. My results look the same and still I can access Microsoft and log in to TQ just fine.
Same thing with amazon.com and ibm.com.
I’m not stating everything is fine with TQ, just trying to point out that these traceroute results are nothing to panic over as they do not reveal or reliably suggest any issue.
1 Like
Pringles can wifi or Yagi antenna or a 2km reel of cable
2 Likes
6hrs and counting not able to log in to Tranquility at all on any account. However I was able to log into Singularity without a problem on the first attempt.
1 Like
Still unable to connect since this AM. East coast USA.
just here to report issues from USA gmt -6, good luck everyone lol…
1 Like
Unable to connect from Poland
11 40 ms 39 ms 39 ms s-b6-link.telia.net [62.115.139.107]
12 41 ms 42 ms 41 ms amazon-ic-325291-s-b6.c.telia.net [62.115.155.153]
13 55 ms 45 ms 43 ms 52.93.2.96
14 46 ms 49 ms 44 ms 52.93.2.185
15 * * * UpynĄ limit czasu ľĄdania.
16 * * * UpynĄ limit czasu ľĄdania.
17 * * * UpynĄ limit czasu ľĄdania.
Starting tracert for binaries.eveonline.com
11 39 ms 41 ms 42 ms s-b6-link.telia.net [62.115.136.35]
12 41 ms 42 ms 57 ms amazon-ic-325291-s-b6.c.telia.net [62.115.155.153]
13 47 ms 63 ms 56 ms 52.93.2.112
14 43 ms 39 ms 41 ms 52.93.2.187
15 * * * UpynĄ limit czasu ľĄdania.
16 * * * UpynĄ limit czasu ľĄdania.
17 * * * UpynĄ limit czasu ľĄdania.
I DEMAND 1000000(one million) SP as Compensation!!
(oh, sorry, I DEMAND ONE ZIZILION GIZILION SP as Compensation)
(… and 3D printed Venture… with free shipping…)
3 Likes
So is this the Cliff Edge we were warned about in Europe? Fabric of space and time continuum imploding?
1 Like
Can we roll back the launcher? somebody said on Eve Status twitter that they solved it that way
I was able to log on fine, but I really don’t want to risk flying my ship because last time I was in space I lagged out and lost a Vargur
And your rationale for saying I shouldn’t be reimbursed for paying for a service I didn’t receive? There is no rationale, you’re just being a douchebag.
Well it’s not really money anyway, however, I would consider starcakes adequate settlement
1 Like
Well we’re paying real money in subscriptions.
That’s currency, not money
Only as long as I get reimbursed for the Avatar I just found fully fitted with 10k PLEX in the cargohold. And some other stuff like implants that are all worth like billions each or something and there are 100 of them. This legit happened cos I say it did and if the server gets rolled back I will join the entitlement-train here and expect it replaced. Probably.
There is a rationale. I wouldn’t say something I couldn’t back up. It is twofold and goes like this: It isn’t a problem with EVE so ofc you shouldn’t be reimbursed this way as you should be reimbursed by the party at fault. Their details have been posted on these forums more than once already. Additionally, why should you get reimbursed when the Ts&Cs specifically cover this sort of eventuality. Hell, if you read them you should just be happy that they even let you play EVE, and don’t just take your money anyway…
Evexit™
1 Like
can not log in at all, UK. “Could not connect to the specified address. Odds are that you have not established an internet connection, the server isn’t running, or the server address or port number was wrong.”