Sqweellex wrote: Tue Oct 06, 2026 7:14 am
Computer wrote: Mon Oct 05, 2026 7:11 pm
Thanks to the team for their dedication to addressing the issue. I understand there are certain issues out of your hands due to 3rd party providers. As someone who works in infra I know how frustrating it can be to churn through NOC's with incredibly siloed teams and lack of escalation procedure that makes escalation on these types of issues a massive headache.
And for the tourtists crying and threatening to delete their accounts, I know you are incapable of doing so. Prove me wrong.
Take the Log Breaker guild, for instance; it completely fell apart due to DDoS issues. Some members moved to the "Forever" beta, others went to different private projects, while a few—myself included—have stayed here for now. The reason is painfully simple: the DDoS attacks made it nearly impossible to complete a raid properly over the course of a month. We faced constant disconnects and login failures; there was even an incident where the raid leader was banned mid-raid—allegedly for RMT—though, in fairness, the ban was lifted a few hours later. We had to constantly reschedule raids; there were times we rescheduled our Molten Core run three times in a single week. We’d log in and kill a boss, only for some members to get kicked and unable to reconnect, forcing us to postpone the raid by a few hours or until the next day. Then we’d try again, kill one or two bosses, and—bam—more disconnects, leading to another postponement.
Just this past weekend, several members of the guild I joined after Log Breaker disbanded also left the project. They moved to a server that has a low player count but runs stably. People just want to play the game—and here, they simply can't.
Nothing wrong with seeking alternatives while the server encounters issues. And my point wasn't directed at you. It was directed at the manchildren going to the ledge and saying "i'm gonna jump ! " as if that's going to resolve the issue and incur a response any faster. If they took 10 seconds to read between the lines in their prior updates. They would know that this issue is not something to "fix" as the issues are not on the implementation level / server code.
The issue lies with the infrastructure itself such as 3rd party hosting providers ( floki ) and DNS providers ( blazingfast ). Mitigation needs to happen upstream of the server, such as at the hosting provider. Who they are following up on to get updates.
The only thing devs can do at this point is seek out alternatives for DNS and hosting , which they have already mentioned in one of their prior updates ( not easy to do if you want to avoid companies who bend the knee to US subpoenas ) , and hound flokinet and blazingfast.io to get status / request escalation on open tickets. This is without mentioning that moving said infrastructure over to alternate hosting providers will have downtime ( which people will inevitably complain about as well )
Again , this is not directed at you but just pointing out the irony in those wanting updates & info while remaining ignorant as to why there have not been consistent updates. It's a damned if you do , damned if you don't situation.
Because if you provide the same update that these providers have been giving the devs for weeks , then that's not good enough for people and considered "fluff". If you wait to update people then people will gripe about lack of communication.