Matrix Outage History

Matrix is up right now

Matrix had 16 outages in the last 2 years totaling 461h 5m of downtime — averaging 0.7 incidents per month.

There were 16 Matrix outages since June 20, 2025 totaling 461h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.matrix.org

Major May 5, 2026

Performance degradation

Detected by Pingoru
May 05, 2026, 07:00 AM UTC
Resolved
May 05, 2026, 07:00 AM UTC
Duration
Timeline · 1 update
  1. resolved May 05, 2026, 08:06 AM UTC

    Around 07:00 UTC until 08:00 UTC, performance on the matrix.org homeserver was degraded due to a transient problem preventing database maintenance.

Read the full incident report →

Critical April 16, 2026

Problems sending messages via matrix.org

Detected by Pingoru
Apr 16, 2026, 03:05 PM UTC
Resolved
Apr 16, 2026, 10:15 PM UTC
Duration
7h 9m
Affected: Synapse
Timeline · 3 updates
  1. investigating Apr 16, 2026, 03:54 PM UTC

    We are investigating a problem sending messages via the matrix.org homeserver

  2. monitoring Apr 16, 2026, 03:55 PM UTC

    The problem was related to an upgrade to the homeserver on matrix.org. We have rolled back to the previous release, and service has been restored.

  3. resolved Apr 16, 2026, 10:15 PM UTC

    The homeserver has been stable since rolling back. The Synapse team will work on a resolution to the bug that caused the outage.

Read the full incident report →

Major March 19, 2026

Slow outbound federation

Detected by Pingoru
Mar 19, 2026, 11:15 AM UTC
Resolved
Mar 19, 2026, 11:38 AM UTC
Duration
23m
Affected: Outbound federation
Timeline · 2 updates
  1. monitoring Mar 19, 2026, 11:30 AM UTC

    Outbound federation from matrix.org paused for several minutes, and is now catching up.

  2. resolved Mar 19, 2026, 11:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Performance of sending and loading messages is degraded

Detected by Pingoru
Mar 02, 2026, 08:39 PM UTC
Resolved
Mar 04, 2026, 12:18 PM UTC
Duration
1d 15h
Affected: Synapse
Timeline · 3 updates
  1. investigating Mar 02, 2026, 08:39 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 02, 2026, 09:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 04, 2026, 12:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Performance issues regarding message sending on matrix.org

Detected by Pingoru
Mar 02, 2026, 03:20 PM UTC
Resolved
Mar 02, 2026, 06:34 PM UTC
Duration
3h 13m
Affected: SynapseOutbound federation
Timeline · 3 updates
  1. identified Mar 02, 2026, 03:20 PM UTC

    Performance on matrix.org is currently slow due to ongoing device cleanup.

  2. monitoring Mar 02, 2026, 05:22 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 02, 2026, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Sending messages has reduced performance

Detected by Pingoru
Mar 02, 2026, 08:47 AM UTC
Resolved
Mar 02, 2026, 12:04 PM UTC
Duration
3h 17m
Affected: SynapseOutbound federation
Timeline · 2 updates
  1. investigating Mar 02, 2026, 08:47 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 02, 2026, 12:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 24, 2026

Slow logins

Detected by Pingoru
Feb 24, 2026, 08:00 AM UTC
Resolved
Feb 24, 2026, 11:13 AM UTC
Duration
3h 13m
Affected: Synapse
Timeline · 2 updates
  1. investigating Feb 24, 2026, 09:47 AM UTC

    We are currently investigating this issue.

  2. resolved Feb 24, 2026, 11:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026

Degraded performance

Detected by Pingoru
Feb 11, 2026, 06:30 PM UTC
Resolved
Feb 12, 2026, 05:07 AM UTC
Duration
10h 37m
Affected: Synapse
Timeline · 2 updates
  1. investigating Feb 11, 2026, 06:30 PM UTC

    Due to a substantial increase in traffic, performance is currently degraded.

  2. resolved Feb 12, 2026, 05:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 13, 2025

Degraded performance across client endpoints

Detected by Pingoru
Oct 13, 2025, 08:57 AM UTC
Resolved
Oct 13, 2025, 11:35 AM UTC
Duration
2h 38m
Affected: Synapse
Timeline · 3 updates
  1. investigating Oct 13, 2025, 08:57 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 13, 2025, 09:27 AM UTC

    The degraded performance was linked to a harmless error which nevertheless was being reported millions of times per hour, affecting CPU. We've fixed the error and service appears to be stabilising.

  3. resolved Oct 13, 2025, 11:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 2, 2025

Database incident

Detected by Pingoru
Sep 02, 2025, 05:39 PM UTC
Resolved
Sep 04, 2025, 09:28 AM UTC
Duration
1d 15h
Affected: Synapse
Timeline · 6 updates
  1. identified Sep 02, 2025, 05:39 PM UTC

    We've identified an issue with the matrix.org database

  2. identified Sep 02, 2025, 07:42 PM UTC

    We are in the process of restoring the matrix.org database from a backup. The matrix.org homeserver will be offline until this has been completed

  3. identified Sep 03, 2025, 08:49 AM UTC

    Restoration is ongoing, we do not yet have a concrete estimate for resolution. Live updates here https://bsky.app/profile/matrix.org/post/3lxuslbzjuc2t

  4. monitoring Sep 03, 2025, 05:03 PM UTC

    The database has been restore, and verification checks complete. matrix.org's Synapse has been started up again and we are monitoring

  5. monitoring Sep 03, 2025, 05:37 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Sep 04, 2025, 09:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2025

matrix.org federation outage

Detected by Pingoru
Jul 31, 2025, 08:59 PM UTC
Resolved
Aug 01, 2025, 09:29 AM UTC
Duration
12h 30m
Affected: SynapseOutbound federation
Timeline · 4 updates
  1. investigating Jul 31, 2025, 08:59 PM UTC

    We are investigating continued problems with inbound federation on the matrix.org homeserver

  2. investigating Jul 31, 2025, 09:01 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 31, 2025, 09:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 01, 2025, 09:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 31, 2025

Matrix.org Federation Outage

Detected by Pingoru
Jul 31, 2025, 08:04 PM UTC
Resolved
Jul 31, 2025, 07:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Jul 31, 2025, 08:04 PM UTC

    matrix.org inbound federation was inoperable from roughly 18:55 UTC to 20:00 UTC due to a logic error during a code roll out. The issue is now resolved.

Read the full incident report →

Minor July 2, 2025

Actions such as message sending or invites is failing in a small subset of rooms

Detected by Pingoru
Jul 02, 2025, 03:38 PM UTC
Resolved
Jul 16, 2025, 09:03 AM UTC
Duration
13d 17h
Affected: Synapse
Timeline · 5 updates
  1. investigating Jul 02, 2025, 03:38 PM UTC

    We're investigating reports of broken functionality in federated and unfederated rooms that contain matrix.org users. As a workaround, one can create a new room and continue communicating there. We are working to identify the cause and correct the affected rooms.

  2. investigating Jul 04, 2025, 10:11 AM UTC

    We are still working to determine the root cause, which currently appears to only originate on the matrix.org homeserver. In the meantime, we've devised a fix and will be attempting that shortly.

  3. investigating Jul 08, 2025, 01:01 PM UTC

    We are still working to restore all affected rooms

  4. identified Jul 11, 2025, 09:46 AM UTC

    We believe we have restored the majority of the affected rooms. We are working on verifying and identifying any remaining rooms that may have been affected.

  5. resolved Jul 16, 2025, 09:03 AM UTC

    We believe that all of the affected rooms have been fixed.

Read the full incident report →

Major June 26, 2025

Logging in to matrix.org is experiencing intermittent failures

Detected by Pingoru
Jun 26, 2025, 04:34 PM UTC
Resolved
Jun 27, 2025, 12:48 AM UTC
Duration
8h 13m
Affected: Synapse
Timeline · 4 updates
  1. investigating Jun 26, 2025, 04:34 PM UTC

    We are currently investigating this issue.

  2. identified Jun 26, 2025, 04:49 PM UTC

    The issue is due to degraded DB performance. We've identified what's slowing the DB down and cleaning it up.

  3. monitoring Jun 26, 2025, 07:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 27, 2025, 12:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 20, 2025

Degraded performance on matrix.org Synapse

Detected by Pingoru
Jun 20, 2025, 10:12 AM UTC
Resolved
Jun 20, 2025, 10:27 AM UTC
Duration
15m
Affected: Synapse
Timeline · 5 updates
  1. investigating Jun 20, 2025, 10:12 AM UTC

    We're currently identifying the root cause for degraded performance on matrix.org's Synapse instance.

  2. investigating Jun 20, 2025, 10:12 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 20, 2025, 10:19 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Jun 20, 2025, 10:23 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jun 20, 2025, 10:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 20, 2025

General degraded performance since 02h00 UTC

Detected by Pingoru
Jun 20, 2025, 03:21 AM UTC
Resolved
Jun 20, 2025, 04:01 AM UTC
Duration
39m
Affected: Synapse
Timeline · 2 updates
  1. investigating Jun 20, 2025, 03:21 AM UTC

    We are currently investigating this issue.

  2. resolved Jun 20, 2025, 04:01 AM UTC

    The database performance issue has now been identified and resolved.

Read the full incident report →