mastodon.social Outage History

mastodon.social is up right now

mastodon.social had 11 outages in the last 2 years totaling 217h 53m of downtime — averaging 0.5 incidents per month.

There were 11 mastodon.social outages since November 3, 2025 totaling 217h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://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 →

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
May 28, 2026, 03:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 28, 2026, 03:00 PM UTC

    Type: Incident Duration: 5 days, 21 hours and 24 minutes Affected Components: Website & API May 28, 15:00:00 GMT+0 - Identified - 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. May 28, 19:56:29 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 3, 12:23:39 GMT+0 - Resolved - 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 →

Minor April 20, 2026

DDoS

Detected by Pingoru
Apr 20, 2026, 10:58 AM UTC
Resolved
Apr 20, 2026, 10:58 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 20, 2026, 10:58 AM UTC

    Type: Incident Duration: 21 hours and 15 minutes Affected Components: Website & API, Background queues Apr 20, 10:58:33 GMT+0 - Investigating - We are currently experiencing a DDoS attack. We are actively investigating the issue. Apr 20, 13:05:28 GMT+0 - Monitoring - We have implemented countermeasure against the DDoS attack, and the site is accessible. We are continuing to monitor the situation. Apr 21, 08:13:37 GMT+0 - Resolved - The attacks seem to have stopped, all operations have returned to normal.

Read the full incident report →

Major February 25, 2026

Hetzner Outage

Detected by Pingoru
Feb 25, 2026, 09:08 PM UTC
Resolved
Feb 25, 2026, 09:08 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 25, 2026, 09:08 PM UTC

    Type: Incident Duration: 27 minutes Affected Components: Website & API, Streaming API, Background queues Feb 25, 21:08:32 GMT+0 - Investigating - Hetzner, our cloud provider, appears to be having a significant outage, leaving many of our resources unavailable. We are monitoring the issue. Feb 25, 21:16:30 GMT+0 - Monitoring - Services have been restored and Hetzner connectivity seems to have returned. Will continue to monitor the situation. Feb 25, 21:35:12 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor December 17, 2025

Connectivity/timeout issues with sidekiq

Detected by Pingoru
Dec 17, 2025, 02:00 PM UTC
Resolved
Dec 17, 2025, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 17, 2025, 02:00 PM UTC

    Type: Incident Duration: 12 days, 18 hours and 22 minutes Affected Components: Website & API, Background queues Dec 17, 14:00:00 GMT+0 - Investigating - There appears to be an issue with connection timeouts to our Sidekiq runners, causing some operations to take longer than expected, or require multiple tries. We are currently investigating this issue. Jan 18, 09:22:00 GMT+0 - Resolved - Sidekiq has been stable, so considering this incident resolved. Jan 7, 06:42:57 GMT+0 - Monitoring - We found out the cause for this issue (within a dependency) and we deployed a fix 8 hours ago. So far, it seems to have completely fixed the issue.

Read the full incident report →

Major November 3, 2025

Website is down due to database issue

Detected by Pingoru
Nov 03, 2025, 05:20 PM UTC
Resolved
Nov 03, 2025, 05:20 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 03, 2025, 05:20 PM UTC

    Type: Incident Duration: 8 minutes Affected Components: Website & API, Background queues Nov 3, 17:20:27 GMT+0 - Identified - [mastodon.social](http://mastodon.social) is currently unresponsive to a database issue. We identified the problem and are working on fixing it. Nov 3, 17:28:47 GMT+0 - Resolved - This incident has been resolved, everything is now operational again.

Read the full incident report →