Mastodon says its flagship server was hit by a DDoS attack

Mastodon, the decentralized social networking platform, reported that its primary server was subjected to a distributed denial-of-service (DDoS) attack on Monday, causing significant accessibility issues. Users encountered error messages and full-screen outage alerts, rendering the site unusable at various times throughout the day. In a status update issued around 7 a.m. ET, Mastodon acknowledged the ongoing cyberattack and indicated that they were actively investigating the situation. By approximately 9:05 a.m. ET, the team announced that they had implemented a countermeasure to mitigate the DDoS attack, restoring access to the site. However, they cautioned users that intermittent instability might persist as the attack was still in progress. This incident follows closely behind a similar DDoS attack experienced by Bluesky, another decentralized social network, which recently resolved a series of outages attributed to a prolonged cyber assault. Bluesky reported that while the DDoS attack continued as of April 17, service stability had returned since April 16 at 9 PM PDT. Mastodon representatives did not provide immediate comments on the motivations behind the attack when approached for additional information by TechCrunch. DDoS attacks work by inundating a website or application’s servers with an overwhelming volume of traffic, aiming to disrupt service rather than steal data. Over the years, DDoS attacks have grown in size and intensity. In a notable example from the previous year, Cloudflare reported mitigating a massive attack that peaked at 29.7 terabits per second, an enormous volume of data comparable to filling thousands of hard drives every minute. While such attacks can cause significant disturbances to larger platforms, they do not necessarily affect all users. For instance, Bluesky users who migrated their accounts to other providers that share the same protocol experienced no impact during the attack. Similarly, the DDoS assault on Mastodon appears to have primarily targeted its main server, mastodon.social, while many smaller instances within the Mastodon network remained unaffected.