mastodon.social Outage History

mastodon.social is up right now

mastodon.social had 11 outages in the last 2 years totaling 906h 22m of downtime, averaging 0.5 incidents per month.

There were 11 mastodon.social outages since November 3, 2025 totaling 906h 22m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.mastodon.social

Major October 1, 2026

Hetzner Connectivity Issues

Detected by Pingoru
Oct 01, 2026, 08:49 AM UTC
Resolved
Oct 02, 2026, 02:07 PM UTC
Duration
1d 5h
Affected: Website & APIBackground queues
Timeline · 5 updates
  1. investigating Oct 01, 2026, 08:49 AM UTC

    We are experiencing connectivity issues with our servers within Hetzner. We are investigating the issue.

  2. investigating Oct 01, 2026, 09:01 AM UTC

    Hetzner is reporting vSwitch outages, which are likely the cause of our connectivity issues. We are monitoring and continuing to look for workarounds.

  3. monitoring Oct 01, 2026, 10:57 AM UTC

    Cluster connectivity is slowly returning, and all services are operation, though at reduced performance. We are continuing to monitor the situation.

  4. monitoring Oct 01, 2026, 03:07 PM UTC

    Performance has returned to normal. We will continue to keep an eye on the situation.

  5. resolved Oct 02, 2026, 02:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 25, 2026

Website and API is down

Detected by Pingoru
Sep 25, 2026, 07:43 AM UTC
Resolved
Sep 25, 2026, 08:09 AM UTC
Duration
26m
Affected: Website & API
Timeline · 2 updates
  1. investigating Sep 25, 2026, 07:43 AM UTC

    We are currently investigating this incident.

  2. resolved Sep 25, 2026, 08:09 AM UTC

    This was caused by a migration, which has been rolled back. All services are back online.

Read the full incident report →

Minor September 21, 2026

Degraded performance on API and website

Detected by Pingoru
Sep 21, 2026, 03:30 PM UTC
Resolved
Oct 20, 2026, 07:58 AM UTC
Duration
28d 16h
Affected: Website & API
Timeline · 2 updates
  1. investigating Sep 21, 2026, 03:30 PM UTC

    We are experiencing performance degradation and higher than usual error rates on the API and the web interface. As we are currently making changes to our infrastructure we initially thought it was the cause and rolled it back, but the service is still degraded and it does not seem to be related to our migration. We are investigating the source further.

  2. monitoring Sep 22, 2026, 06:46 PM UTC

    Situation is now stable. We will continue keeping a close look on the performance for the next few days while we continue our infrastructure changes.

Read the full incident report →

Major August 19, 2026

Website inaccessible

Detected by Pingoru
Aug 19, 2026, 02:41 PM UTC
Resolved
Aug 19, 2026, 03:06 PM UTC
Duration
25m
Affected: Website & API
Timeline · 3 updates
  1. investigating Aug 19, 2026, 02:41 PM UTC

    We are currently investigating this incident.

  2. identified Aug 19, 2026, 02:47 PM UTC

    It's DNS.

  3. resolved Aug 19, 2026, 03:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 5, 2026

Elasticsearch issues

Detected by Pingoru
Aug 05, 2026, 03:07 PM UTC
Resolved
Aug 06, 2026, 05:21 PM UTC
Duration
1d 2h
Affected: Website & API
Timeline · 4 updates
  1. investigating Aug 05, 2026, 03:07 PM UTC

    There appears to be an issue with our Elasticsearch cluster that is causing the instance to fail. We are currently investigating the issue.

  2. identified Aug 05, 2026, 04:00 PM UTC

    We identified the source of the abnormal search trafic and are working on a solution

  3. monitoring Aug 05, 2026, 05:43 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Aug 06, 2026, 05:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026

Performance degradation

Detected by Pingoru
May 28, 2026, 03:00 PM UTC
Resolved
Jun 03, 2026, 12:23 PM UTC
Duration
5d 21h
Affected: Website & API
Timeline · 3 updates
  1. identified May 28, 2026, 03:00 PM UTC

    We are having issues with the caching server used by mastodon.social, which is causing increased latency and intermittent errors. We are working on implementing a solution.

  2. monitoring May 28, 2026, 07:56 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jun 03, 2026, 12:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 23, 2026

DDoS attack in progress

Detected by Pingoru
Apr 23, 2026, 09:48 AM UTC
Resolved
Apr 24, 2026, 05:54 AM UTC
Duration
20h 5m
Affected: mastodon.socialWebsite & APIBackground queuesMedia storageStreaming API
Timeline · 4 updates
  1. identified Apr 23, 2026, 09:48 AM UTC

    We are (again) targeted by a DDoS attack and [mastodon.social](http://mastodon.social) may not be available while we mitigate it.

  2. monitoring Apr 23, 2026, 10:05 AM UTC

    We have enabled DDoS protection methods, and services is mostly restored. We still continue to monitor the situation.

  3. monitoring Apr 23, 2026, 10:40 AM UTC

    The attack seems to have stopped. We are continuing to monitor the situation.

  4. resolved Apr 24, 2026, 05:54 AM UTC

    This incident has been resolved.

Read the full incident report →