Yeah, for pathetic losers. People who have any semblence of self-esteem don’t need to take joy in the suffering of others.
can this be called a more realistic version of what blackout should have been like? random stuff relating to chats and a seemingly random local setup 0.o
nah serious note mate thanks for the update was wondering why my alts wasnt in corp and my alliance leader toon wasnt in an alliance lol
Sadly, the chat and login difficulties remain unabated for me.
I can still login, but chat is still not connecting - both throw error messages.
whelp…doesnt look like i’m logging in today either far as the login screen is going…time to go back into RL hibernation 
good luck everyone
set me vpn to UK and got in w chat working. JS
its been 40 minutes but i am Finally at the Character select screen.
This is what I did.
- I contacted Neustar and talked to them about the issues.
- I then posted a link.
- I then posted a link to Brian flipping out.
- I posted the same video link on DJT’s FB page.
- I then redacted the post with a link and got in.
Ukraine, Dniepropetrovsk
Starting traceroute diagnostics - this may take several minutes
Starting tracert for launcher.eveonline.com
Трассировка маршрута к d1hoqe10mv32pv.cloudfront.net [143.204.101.31]
с максимальным числом прыжков 30:
1 <1 мс <1 мс <1 мс 192.168.0.1
2 1 ms <1 мс <1 мс 178-137-11-253.broadband.kyivstar.net [178.137.11.253]
3 17 ms 13 ms 13 ms 81-23-23-77.ip.kyivstar.net [81.23.23.77]
4 22 ms 24 ms 22 ms bpt-b4-link.telia.net [80.239.128.61]
5 37 ms 37 ms 38 ms prag-bb1-link.telia.net [62.115.118.180]
6 41 ms 41 ms 41 ms ffm-bb3-link.telia.net [62.115.121.118]
7 41 ms 41 ms 43 ms ffm-b5-link.telia.net [62.115.114.89]
8 37 ms 36 ms 36 ms amazon-ic-331704-ffm-b4.c.telia.net [62.115.57.137]
9 40 ms 41 ms 40 ms 52.93.111.8
10 56 ms 39 ms 40 ms 54.239.107.111
11 39 ms 39 ms 39 ms 54.239.5.55
12 38 ms 46 ms 45 ms 54.239.106.154
13 41 ms 41 ms 41 ms 54.239.4.137
14 * * * Превышен интервал ожидания для запроса.
15 * * * Превышен интервал ожидания для запроса.
16 * * * Превышен интервал ожидания для запроса.
17 * * * Превышен интервал ожидания для запроса.
18 * * * Превышен интервал ожидания для запроса.
19 41 ms 41 ms 41 ms server-143-204-101-31.fra50.r.cloudfront.net [143.204.101.31]
Трассировка завершена.
Starting tracert for binaries.eveonline.com
Трассировка маршрута к d17ueqc3zm9j8o.cloudfront.net [13.224.187.35]
с максимальным числом прыжков 30:
1 <1 мс <1 мс <1 мс 192.168.0.1
2 <1 мс <1 мс <1 мс 178-137-11-253.broadband.kyivstar.net [178.137.11.253]
3 9 ms 9 ms 9 ms 81-23-23-74.ip.kyivstar.net [81.23.23.74]
4 8 ms 7 ms 7 ms be5877.rcr22.kbp01.atlas.cogentco.com [149.6.190.65]
5 26 ms 26 ms 25 ms be2047.ccr22.bts01.atlas.cogentco.com [154.54.60.205]
6 25 ms 24 ms 25 ms be3463.ccr52.vie01.atlas.cogentco.com [154.54.59.185]
7 33 ms 33 ms 33 ms be3462.ccr22.muc03.atlas.cogentco.com [154.54.59.182]
8 37 ms 37 ms 36 ms be2960.ccr42.fra03.atlas.cogentco.com [154.54.36.253]
9 42 ms 41 ms 52 ms amazon.demarc.cogentco.com [149.14.159.194]
10 39 ms 40 ms 39 ms 52.93.111.0
11 38 ms 39 ms 41 ms 54.239.107.17
12 37 ms 37 ms 37 ms 54.239.4.219
13 45 ms 40 ms 43 ms 54.239.106.38
14 39 ms 39 ms 40 ms 52.93.244.107
15 * * * Превышен интервал ожидания для запроса.
16 * * * Превышен интервал ожидания для запроса.
17 * * * Превышен интервал ожидания для запроса.
18 * * * Превышен интервал ожидания для запроса.
19 * * * Превышен интервал ожидания для запроса.
20 36 ms 36 ms 36 ms server-13-224-187-35.fra2.r.cloudfront.net [13.224.187.35]
Трассировка завершена.
Starting tracert for resources.eveonline.com
Трассировка маршрута к dm794883twbxj.cloudfront.net [143.204.91.45]
с максимальным числом прыжков 30:
1 <1 мс <1 мс <1 мс 192.168.0.1
2 <1 мс <1 мс <1 мс 178-137-11-253.broadband.kyivstar.net [178.137.11.253]
3 13 ms 13 ms 13 ms 81-23-23-77.ip.kyivstar.net [81.23.23.77]
4 24 ms 24 ms 24 ms bpt-b4-link.telia.net [80.239.128.61]
5 38 ms 39 ms 38 ms prag-bb1-link.telia.net [62.115.118.180]
6 43 ms 42 ms 42 ms ffm-bb3-link.telia.net [62.115.121.118]
7 45 ms 45 ms 43 ms ffm-b5-link.telia.net [62.115.114.89]
8 44 ms 38 ms 38 ms amazon-ic-331704-ffm-b4.c.telia.net [62.115.57.137]
9 49 ms 40 ms 39 ms 52.93.111.12
10 41 ms 43 ms 41 ms 54.239.107.151
11 41 ms 40 ms 40 ms 54.239.4.250
12 43 ms 49 ms 44 ms 54.239.106.40
13 43 ms 40 ms 40 ms 54.239.4.123
14 * * * Превышен интервал ожидания для запроса.
15 * * * Превышен интервал ожидания для запроса.
16 * * * Превышен интервал ожидания для запроса.
17 * * * Превышен интервал ожидания для запроса.
18 * * * Превышен интервал ожидания для запроса.
19 41 ms 41 ms 41 ms server-143-204-91-45.fra50.r.cloudfront.net [143.204.91.45]
Трассировка завершена.
Traceroute diagnostics finished
Why don’t you switch off the chat service?
We know it is currently broken.
Why keep it up, so some can get local wile others can not.
If you one of those lucky to connect to the broken local you still have huge advantage over those that can not connect to any chat at all.
Fix the “bug out” by making it “black out” !
Chat is still not working for me. I get a connection error popup message in-game
Clicking ‘yes’ doesn’t work.
Thank you for finally acknowledging these issues, I have lost so many ships due to these constant disconnects and contracts, are these tickets ever going to be answered?
I dont know why they just havent shut the server down for emergency maintenance in general. Take some time to fix it instead of allowing it to be half fast repaired
2 Likes
I’ve been saying for weeks that when CCP can’t protect their system they need to do three things:
- Shut off fuel consumption by stations.
- Shut off PVP (so the lucky few who do get in don’t have an unnatural advantage over those of us who are stuck in lag- or serial-DC-hell).
- Automatically credit every player in Omega status the day.
That’s the honorable and reasonable approach to this.
Now, whether CCP is going to behave in an honorable and reasonable manner…
I’ve already canceled all six of my Omega accounts and told CCP that I won’t be restarting them until they recompense me fully for all losses (Omega time for the many, many lost days and in-game losses for fuel costs (can’t get anyone to buy my merch or use my services if they can’t log in), probe losses (DC’d between clicking “Recall Probes” and them actually coming back and couldn’t get back in for six hours - they disappeared), ship losses (Orca, four Procurers, three Gilas so far)).
Every player with an Omega account in the game should cancel his or her Omega status and notify CCP that they won’t be getting any more cash from us until they FULLY reimburse us for their utter lack of preparedness for the most predictable cyber attack ever.
Banks, telecoms, other games, they all get hit by these and none of them are this damaged for this long.
They NEED to shut the whole thing down until they fix it - shut off the timers so no one’s station burns up all its fuel, no one loses any timers on on-going attacks - just shut the game off until they (if needed) hire network security folks who know something more about network security than “Blame Amazon Web Services”.
1 Like
What I am finding overall is chat will randomly either start out connected, or I will get the chat error. I have found that saying something in a chat channel and then choosing from the pop-up about the chat yes and no at least once will seem to cause me to reconnect to chat. The only persistent issue after that is that often Local is unreliable in terms of the actual local count of pilots (confirmed with alts in the same system). It can take a few minutes sometimes when I login and the chat server isn’t connecting for me, but I do get it working as per above. I hope this can help some of you in the meantime as a workaround to get your chat working.
Logging into the game isn’t an issue. If I get the unable to connect I will either try again or simply click on the “Connect” button option after closing the pop-up window.
took 40 minute to get in game, within 5 minutes got a connection time out. Thanks but that’s it for me, I won’t even be able to update my PI now before i go to work
Will there be any reimbursement of lose ships and mods due to the lost of connection.
That worked for me for a day, but now not even that works. That is what is most frustrating, it has actually gotten worse for some of us since they started trying to fix it.
at this point someone having connection issues shouldnt be undocking to try losing ships to begin with but yeah, open a ticket and they’ll review the losses, include a killboard/killmail link or some such
grab your towel, it’s gonna be a long trip lol
1 Like
Blockquote
Take your own advise?