They're doing their "Countermeasures"
lmao
One wonders how any other MMORPG is doing perfectly fine DDOS wise, and even FPS games are doing fine.
But please, do keep excusing mediocrity.
About a year ago (Sept. 2023), Destiny 2 was DDOS'd non-stop for a week straight (as in throughout virtually the entire day, every day, rather than one brief specific window late at night).
WoW has been hit with periodic DDOS attacks throughout its entire existence, including multiple easily searchable examples in just the past year alone.
The reality is that "any other MMO" isn't doing perfectly fine - most successful ones experience this on a rather frequent basis. It just happens to be FFXIV's "turn" now, so to speak.
FF14 is DDoS'd for an entire month now so what's your point ?About a year ago (Sept. 2023), Destiny 2 was DDOS'd non-stop for a week straight (as in throughout virtually the entire day, every day, rather than one brief specific window late at night).
WoW has been hit with periodic DDOS attacks throughout its entire existence, including multiple easily searchable examples in just the past year alone.
The reality is that "any other MMO" isn't doing perfectly fine - most successful ones experience this on a rather frequent basis. It just happens to be FFXIV's "turn" now, so to speak.
Chloe
Probably it is your ignorance
The only way to counter DDOS attack is having larger bandwidth than the attacker
Not sure why you think “DDOS resistance server is a thing”
Did you on purpose ignore the fact of Lizzard Squad attack PSN during the Christmas in 2014?
Are you taking DDOS attack as some sort of flu and if you takes medic and it will go away?
Last edited by Divinemights; 09-26-2024 at 01:09 PM.
it's pretty amusing you keep posting from this account considering the thread ranting and raving about false advertising which led you to supposedly get a chargeback
should've retired this one
Really? A DDOS resistant server from Amazon, huh? That seems like a really nice trick, considering when I just tried searching Amazon for such a thing it came up with server aprons for people in food service jobs (top options) and server hardware that does not claim to be resistant to DDOS attacks. In fact, I can find no information on such hardware even existing.
As someone who works in IT and specifically with AWS, I can confirm there is no such thing as DDOS resistant servers and anyone claiming such is a definitive liar.
At the end of the day, there are no good (for an MMO) and definitive ways to stop a DDOS attack, only delay. Now while there are practices that can help remediate, like adding proxy servers which can slow down or limit the incoming traffic, such a solution will also directly affect the playerbase, specifically in the form of very long queues or massive delays between client and server (registering attacks, GCDs not working, aoe damage being pooled together than landed simultaneously when it catches up etc), all of which would make XIV unplayable anyway.
Not to mention the amount of money that would be required monthly to create such an environment via AWS to protect all servers would be likely in the millions. Only the government would even consider going such a route.
Last edited by Havenchild; 09-26-2024 at 07:43 PM.
No there is no HW existing to prevent a DDoS, you can use a Firewall(cluster) to get rid of some background noise, but only working for ~4-10GB/s and no guarantee it's working for specialized attacks.Really? A DDOS resistant server from Amazon, huh? That seems like a really nice trick, considering when I just tried searching Amazon for such a thing it came up with server aprons for people in food service jobs (top options) and server hardware that does not claim to be resistant to DDOS attacks. In fact, I can find no information on such hardware even existing.
Normally DCs are routing your IPs to NULL if a limit of X-GB/s is exceeded. ¯\_(ツ)_/¯
I think Chloe is refering to the situation 10 years ago.
Amazon DCs were able to filter the backgroundnoise to real nice degree, but to get rid of bigger attacks you had to do your part:
- Setup a couple of EC2 proxy instances with the right ports exposed to the internet
- Bundle the addresses in your A record subdomain entry and use a TTL of 60
- Every EC2 has a vpn-tap to the gameservers (selfexplaining the IPs of these end-servers aren't publicly known) and some filter-rules
If you were using 10 instances the botnet had to do a DNS lookup and only seen one IP and every 60 seconds an other one.
If they started an attack, they attacked the current seen address, Amazon was routing the IP to NULL and the instance was down.
Now you can't move a botnet to a new destination real quick, so you have to wait ~5 minutes until they stopped attacking the current one and move to the new target from the DNS lookup.
If you are lucky they'll get the same address again and DDoS a dead instance or just refused to attack, cuz the IP was down.
That's basically what we did long time ago and it was working really nice 9/10 players loved this trick.
But this was never a complete server related thing, it's a mix of both routing and server (the server had the additional filter-rules) and you'll sacrifice one instance on purpose, when a DDoS happens.
But now you can't/woudn't do this anymore for some reasons:
- You'll pay Amazon money for every byte transmitted and a DDoS is getting expensive
- You have to scale the whole thing up to a certain point where it doesn't makes any sense from a cost perspective
- Since we have Cloudflare some Botnets are collecting the addresses of the A record
- Botnets are much better in targetting now, they are even capable of splitting the capacity to multiple targets
Or is Chloe refering to the optional Firewall setting from Amazon? But this option was only capable of filtering up to 2-4GB/s at this time.
Even a cheap botnet exceeded this capacity by a factor of 2 and this was enough to trigger the NULL rule of the DC.
Last edited by GiR_Zippo; 09-26-2024 at 08:18 PM.
The delays were the reason why we were happy when Amazon opened a DC next to our. Normal ping + 5ms to our DC, this was perfect, instead of ping + 50ms from Ireland.Now while there are practices that can help remediate, like adding proxy servers which can slow down or limit the incoming traffic, such a solution will also directly affect the playerbase, specifically in the form of very long queues or massive delays between client and server (registering attacks, GCDs not working, aoe damage being pooled together than landed simultaneously when it catches up etc), all of which would make XIV unplayable anyway.
But as I said, this was long time ago.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.