DDoS Attacks Confirmed

[Just-Communication]

Some of you people don't realize how pervasive these kinds of things are. Ask anyone who deals with Internet security - the vectors are numerous and it is difficult to locate the real culprit(s). Why do you think governments are investing more resources in cyberwarfare? It's a reality folks and anyone who thinks otherwise is a fool. What the notice does tell us is that SE was unable to successfully mitigate and address the threat; no company of repute would want to admit that a third-party attack has crippled their resources - if they were able to deal with it, they would have. Publishing the news is a decision to buffer the negativity due to the technical problems caused by this issue. Can it be considered an excuse? Sure. But they say SE is outright lying is just stupid. The attackers can celebrate that they've been acknowledged.

[CaelThunderwing]

honestly i'm the fence on the matter,

if we look at how SB was rushed, Hyped (this can lead to a legit group wanting to slap em down for it w/ a legit DDoS), how we had no word about matters till almost last min, how after thousands upon thousands of outcries by the players this downtime affected (people who cant play often in a day , those that only get to play much durring a day off, or when RL lets them,) with no signs of Any compensation (lets be real people want subtime extension but fat chances people, a more realistic would of been acceptable of ingame items, and we might get something when matters actually settle.), initial attempts to pass this off as them wanting us to leave highly congested worlds (splitting/fracturing teh player base, incentivizing of making friends leave one another /doing harm to those worlds ingame economies or FreeCompany/LS communities.) one Could look at this with a cynical view like this and only help but say its just an excuse to save face for gross incompetence on developer parts on testing SB's Code to ensure it wouldn't adversely affect live "Production" servers (its a major sin in the networking industry, to run untested experimental code on a live production server when you have no idea how it could affect it. think of this is how 2.0 launch was horrible but fixed shortly after as it went thru many proper beta phases and was a result of them under-expecting how much the fanbase of teh franchise would flock to what once was a severe flop and PR Disaster, how HW/3.0 had issues day 1 but fixed right after.)

but it's not like its not happened to them before, two major times it Occurred in FFXI, once in 2006 (around June) that caused for about a week straight instabilities with World Servers, causing Massive latency to the worlds affected,them to crash and go offline for hours at a time. , then again in 2009, where after a more complex attack brought the Whole lot of the world servers to go offline and "PlayOnline"(yea remember that?)(which for compared to XIV acted as a Lobby Server) to become highly unresponsive or lock players out for over 9 hours.

now maybe im over-analyzing things, but i want to believe its real and just a repeat of whats happened in the past. for what we could end up knowing its a group of (ex) Players that were highly unhappy with 4.0's Job changes (since everything was fine till hours into game going online w/ SB EA and 4.0's changes.) and other online games having seen the same treatment by a mass of players unhappy with an event, changes made, how some ingame matters handled (go look at the rocky history over the last year andhalf for Digital Extremes and thier game, Warframe.). XIV's players i would like to hope are better than resorting to petty shit like this over changes to game mechanics and that it is some group like LizardSquad Responsible.

[Mikhaill]

So this DDOS attack is the main reason why we've been having a horrible ass time with the game so far?
Rauhbah/Pipin/Susano bug? The mass DC's out of the blue then throws us in hour long Q's?
I hate to say it honestly, but I hope it's true. I just can't believe that after all these years they hadn't expected
how launches would go, and especially with the server move and stuff. I just hope it's fixed soon because it surely
surpassed HW launch, this is pretty bad and now kinda unacceptable since this is now "launch". :/

[Felyni]

Ah, so that's why I had CONSTANT DC'S playing on Mateus last night...and couldn't even do my MSQ instances lol....Never DC'd like that before....Hopefully it's playable tonight, having story Q withdrawals.

[Catwho]

Yeah, this is an all of the above scenario.

1. The Raubhan / Pippin walls were a bug with server programming, likely with load balancing, that made it so they only had a fraction of the planned instances available on the virtual servers that handle it. SE acknowledged this. That was mostly fixed by Sunday morning.
2. Susano eating characters was a verified bug and they did a workaround by changing something on Duty Finder until they could get it patched. SE acknowledged this.
3. 3000+ login queues on certain servers was expected, and SE not only warned those players they were gonna have a bad time, they offered free transfers to alleviate the issue. On non congested servers, even during the height of the DDoS spikes, the worst we saw were queues of 500 or so.
4. PS4 download bug was also a verified bug. Also the font and UI size issue, a verified bug. SE acknowledged this.
5. On top of ALL OF THE ABOVE THINGS that SE confirmed, they have now also confirmed that on certain dates, the data center was getting flooded by third party DDoS, compounding all the issues.

Once I got past the walls on Sunday, I have had a pretty smooth time in the game - until last night. The massive disconnects and lag all absolutely match the pattern of a DDoS attack.

[Zenya-kun]

While many people wanna paint SE in a horrible light I'd like to say this. I've had my own gripes with SE for a long time now but the team for FF14 has been bending over backwards for everyone. They are the ones I would trust if anything is said about their servers being attacked. This is the same team and group that admitted fault for a lot of stuff in the past and have been very upfront with everyone. We just gotta give em a lil time.

[silentwindfr]

3. 3000+ login queues on certain servers was expected, and SE not only warned those players they were gonna have a bad time, they offered free transfers to alleviate the issue. On non congested servers, even during the height of the DDoS spikes, the worst we saw were queues of 500 or so.

on this one, i begin to have huge doubt about it, Ragnarok had never any queue time of this size before, even with the patch or HW release...
i feel they have enforce less people per server at the same time, forcing bigger queue for create a need to transfert.

[AkaeiNox]

on this one, i begin to have huge doubt about it, Ragnarok had never any queue time of this size before, even with the patch or HW release...
i feel they have enforce less people per server at the same time, forcing bigger queue for create a need to transfert.

That DDoS attack had nothing to do with the log-in queues, it isn't how it works, they attempted to overload the instance servers with endless requests.

[Kathryn]

on this one, i begin to have huge doubt about it, Ragnarok had never any queue time of this size before, even with the patch or HW release...
i feel they have enforce less people per server at the same time, forcing bigger queue for create a need to transfert.

Tonight will be the second night I cannot log into Ragnarok I've been on the server since 1.0 & never ever before have I ever experienced ques like the ones we are getting currently... I'm kinda getting abit upset the fact I've only managed to lvl to 61.

[Doki]

Don't care, leveled to 70 & beat story.