So the attack is still ongoing, guessing probably better to try login in like tomorrow (not joking) ?
1 Like
the attack is still ongoing ? yes or no ?
Reloaded, recached, restartedâŚstill closed socket.
Maybe ill restart again, and by coincidence the area serving my account/internet will happen to start workingâŚthen I too can be an ass and say âyup, restarting fixed itâ.
Oh, i see. The attacks is still going. But i was told by CCP that the attacks was over. Apparently, itâs not 
Socket still CLOSED!!!
We said that connectivity was restored because the network traffic is now being scrubbed.
2 Likes
Maybe they thought that blocked all attacker`s subnets, but that was mistake.
So are we the customers going to be compensated for this???
jâessaye encore ⌠trying again
pas de chance ⌠no chance
encore une fois ⌠again one time
peut etre ⌠may be
Only if you subscribe to their silly twitter feed or other stupid channel lol
well⌠youâre seemly blocking subnets your PAYING customers are on as well.
I see I am not the only one who still has the closed socket problem ?
No, MANY people obviously have the closed socket problemâŚmyself included
Welcome to EVE Online Forums â thanks for contributing!
Does your reply improve the conversation in some way?
Be kind to your fellow community members.
Constructive criticism is welcome, but criticize ideas, not people.
For more, see our community guidelines. This panel will only appear for your first 2 posts.
Heres an IdeaâŚFIX IT
Well, if thatâs the case, then, when will the people with the closed sockets issues be able to logged back onto Tranquility???
@CCP_Explorer Then why the flipty flip doesnât it say that in the banner!
Connectivity Restored is totally misleading.
Thatâs poor communication, really poor. Now Iâm feking angry at CCP as well.
GET A GRIP
It is an utterly disingenuous , disrespectful, I am gonna treat you like an A-hole response
I had weird problems the last time they did a reboot for an issue. I discovered later that one of my machines worked, and the other didnât. The difference was that one was pointed at google DNS = 8.8.8.8, and the other was pointed at my providerâs DNS. Pointed to google DNS, and did âipconfig /flushdnsâ to clear my DNS cache in windows, and I was able to get online after that.
It seems today is similar. I was also getting âSocket Closed,â but my other machine was working. I tried to clear DNS cache, but that didnât work. So, then I rebooted completely, and it all started working again.
Iâm thinking they have a failover system that updates a public DNS entry. If so, that can take a while to role out globally across DNS. Nothing you can do for that, but wait or use a different DNS server.
1 Like
What they can do is reimburse of for time lost
To be honest, Iâd prefer to criticize both. I mean, this thread is such a target rich environment. How can you not lay into the idiotic, entitled, passive aggressive morons posting here.
Mr Epeen 