DDoS Attack Targets North American Data Center Final Fantasy XIV This Week

Final Fantasy XIV ended a DDoS attack this week that affected service on its North American data center and related servers. While the attack is over, there may still be problems.

The team reported on Wednesday that there were recorded difficulties with the network and that it was due to a DDoS attack. After that, there may have been ongoing issues affecting the player experience, including:

? Disconnected from NA Worlds datacenter

? Difficulty logging in to NA Worlds data centers

? Difficulty accessing, sending and receiving data from NA . data centers

There was an update late in the evening stating that the attack lasted from about 9:53 a.m. to 11:24 a.m. Pacific time on March 9. The update notes that there may still be one more. There are a few issues that need to be resolved in the system, but almost everything will be restored to normal. It’s kind of a relief for a game that’s been hit by demand, which is already comfortable enough to start allowing more players to re-enter, including new players.

On Wednesday, some players reported that their sessions were suddenly interrupted or that they were unable to log in.

Who’s DDOS is using FFXIV rn… I’m in the middle of my daily pvp page

– Shiny?? | Endwalker spoilers (@Shiny_Chariot__) March 9, 2022

While, FFXIV the team is continuing to hunt down spammers and RMT activity. The latest round-up between March 3 and March 9 shows that the team banned 814 accounts for RMT/banned activity and 121 accounts for RMT advertising. These bans come in when the team has confirmed these attempted transactions and spammed through player investigations and reports. The previous report, February 24 to March 3 was even higher, with 4,269 accounts banned for RMT/banned activity, 144 accounts banned from RMT ads, 4 banned and 4 accounts suspended for botting.

Meanwhile, another recent issue with the game, which began allowing players to link their Steam accounts and launch games solely through Steam, has been resolved. The original problem was with the use of non-alphabetic characters in the Steam username.