Final Fantasy 14's NA servers continue to struggle with DDoS attacks, likely due to a service provider's wonky nodes
Some players report a VPN has helped, but it's still grim.
Final Fantasy 14's North American servers have been hammered by DDoS attacks since the release of Patch 7.4—I'd know, I play on them—which has players starting to grind their teeth in frustration. Especially given the release of the latest Savage (high-difficulty) raid tier, and the race to world first that buoys it.
Take a look at the game's official status page, and you'll see notice after notice detailing "recoveries from DDoS" attacks, most of which kicked off in September, primarily affecting North American data centers. On a personal note, most of my gaming sessions, as someone who plays on one of these things, have been interrupted by a DDoS error at some point.
There's also an X account that tracks them, cataloguing them via a website called is.xiv.up.
Have a gander at the r/ffxiv subreddit at the time of writing, and you'll see a legion of players that are (quite rightly) miffed: "Exactly when do we get pissed about this constantly happening?" writes one player. "We have been, it doesn't seem to help," replies another.
In a separate thread, user LastTraintoSector6 writes: "I'm not trying to be alarmist, but I've only been playing about four hours tonight and have been 'DDOS'd' off of Crystal five times … I'm not threatening to unsub, but I do expect better than this from Square-Enix. Because getting booted mid-content is absolutely a complete downer."
At the very least, there've been some killer memes out of the whole fiasco:
Surely One More Year from r/ffxiv
Players aren't particularly charmed on its official forums, either. A now 33-page thread is flooded with complaints. It doesn't help that there are a ton of activities in FF14 where a disconnect will scupper the whole thing: Expensive crafting recipes borked, neck-and-neck enrages with the new endgame raid bosses failed and—I am not kidding, this is a serious issue—windows to catch ultra-rare fish, completely missed.
Keep up to date with the most important stories and the best deals, as picked by the PC Gamer team.
So, why's this happening? Well, given some players have had success with rerouting using VPNs, it's likely a faulty node somewhere along FF14's service provider, NTT. In a—oof, three-year-old, 150-page—thread detailing issues with the provider, user HyperiusUltima notes:
"Yep, it's the Sacramento Node Again. I just ran a tracert and the ping jumps up pretty high at times forcing disconnects. They can't call it DDOS anymore if NTT isn't gonna do their damn job. If anything, can SE just think about changing providers in the future? They are literally SE's Cash Cow right now and they're letting it burn."
If this is the case, then Square Enix might be in a bind, depending on the duration of its contracts with NTT. Either way, it's not a great look for the developer, given director Yoshi-P promised during Dawntrail's release that "we have gone through a process of having perfect defences". Granted, if it is a third-party provider screwing things up, it's out of his hands—but at this point it's time for Square to really put the screws on, or suffer a rightfully-miffed playerbase.
Best MMOs: Most massive
Best strategy games: Number crunching
Best open world games: Unlimited exploration
Best survival games: Live craft love
Best horror games: Fight or flight

Harvey's history with games started when he first begged his parents for a World of Warcraft subscription aged 12, though he's since been cursed with Final Fantasy 14-brain and a huge crush on G'raha Tia. He made his start as a freelancer, writing for websites like Techradar, The Escapist, Dicebreaker, The Gamer, Into the Spine—and of course, PC Gamer. He'll sink his teeth into anything that looks interesting, though he has a soft spot for RPGs, soulslikes, roguelikes, deckbuilders, MMOs, and weird indie titles. He also plays a shelf load of TTRPGs in his offline time. Don't ask him what his favourite system is, he has too many.
You must confirm your public display name before commenting
Please logout and then login again, you will then be prompted to enter your display name.


