Why did Mastodon’s server go down?

Mastodon says its flagship server hit by DDoS

Mastodon said its flagship server was struck by a distributed denial-of-service (DDoS) attack, which rendered the instance unusable at times. In other words, the service couldn’t reliably respond because malicious traffic overwhelmed the infrastructure, leading to intermittent outages and degraded access.

DDoS attacks are designed to flood websites, APIs, or other online services with traffic so that legitimate users can’t connect. For federated social networks like Mastodon, an outage on a major instance can ripple into user experience across the platform, even if only one server is targeted.

What happened operationally: - The company identified the incident as a DDoS attack. - The attack caused the flagship instance to be unusable at times. - The reporting stops short of providing details on attackers’ motivations or whether any data was stolen.

Why it matters: - Mastodon is built on many independently run servers; outages can reduce trust and usability in the local-to-global network. - DDoS events also highlight how availability protections and capacity planning are central for social platforms, especially those that attract attention during political or public-interest moments.

The next practical question for users is whether service stabilizes and how quickly Mastodon can confirm the traffic attack has ended and that defenses are sufficient for sustained uptime. For now, the disruption is directly tied to the DDoS event.