DDoS in process on EQFollow

Well they are at it again.. a DDoS is in process on DayBreak as I post this

This is getting to be quite stupid, trying to play and pay for a game you are not able to play

Problem fixed /crosses fingers

Still going on. I had to bypass the Launcher to get in, but then couldn't create a new char. I was able to log in a char, but was unable to zone.

EDIT: Also cannot access their forums. I get this message: An unexpected database error occurred. Please try again later.

Edited, Dec 30th 2015 2:36pm by KC13

Well, just got home early to play. Cant even load up launcher. Tried to go on EQ.com and nothing. WTF is going on now?

What did we do this time??? Are they Chip Kelly fans???

The first time this happens, I can understand, but after the Nth time, the monkey is on their back for not securing and safeguarding their servers. At this point, they are either unwilling or unable to perform even basic systems administrative functions to maintain access to their servers.

It's not so much EQ as it is the Launcher that they use for all their properties. They need to still allow 'launch screen' login so when some H1Z1 fan gets p*ssed, he can just DDOS H1Z1 and leave EQ alone.

I created a desktop shortcut to the EverQuest2.exe and was able to use it directly.
I am on Win10, so the patcher tool wasn't installed.
I simple entered the desired username/password and was able to login.

I'm going to go out on a limb and say that the number of employees directly working on EQ content/servers has nothing to do with the number of employees that maintain the network itself. And it's the network that was being attacked, not the EQ servers specifically. To be fair to Daybreak though, the first "D" in DDoS is what makes it difficult to deal with. You basically have to black hole every IP that's involved in the attack, with the problem being that you have to be able to distinguish between legitimate and malicious traffic (and some DDoS tools are pretty clever about hiding this). It's all the numbskulls who allow their systems to get hacked and used as platforms for these sorts of attacks that make them successful. On the flip side, given they have been the target of such attacks in the past, you'd think that they'd have some sort of semi-automated process for blocking one once it occurs.

And on the double flip side, when they turn on such protective processes, it's entirely possible that some of the legitimate traffic gets blocked as well, thus leading folks to the "I can't log in!" problem rather than the "it's slow as heck!" problem. Um... And that doesn't count those users of the site whose systems might actually be being used as part of the attack without their knowledge. If there's an attack like this, and after/during it, you find you can't log in at all, you might just want to check your own system (and all systems on your home network) for malware. You could be part of the problem.