Matrix.org

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-03 00:16 UTC

   We are aware of degraded performance on the Matrix.org homeserver. We are additionally aware of failures when trying to log in, caused by the performance degradation.

2. resolved 2026-08-03 11:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-05 07:00 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.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-16 15:05 UTC

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

2. monitoring 2026-04-16 15:55 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 2026-04-16 22:15 UTC

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

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Outbound federation

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-03-19 11:15 UTC

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

2. resolved 2026-03-19 11:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-02 20:39 UTC

   We are currently investigating this issue.

2. monitoring 2026-03-02 21:13 UTC

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

3. resolved 2026-03-04 12:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-02 15:20 UTC

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

2. monitoring 2026-03-02 17:22 UTC

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

3. resolved 2026-03-02 18:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-02 08:47 UTC

   We are currently investigating this issue.

2. resolved 2026-03-02 12:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-24 08:00 UTC

   We are currently investigating this issue.

2. resolved 2026-02-24 11:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-11 18:30 UTC

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

2. resolved 2026-02-12 05:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-13 08:57 UTC

   We are currently investigating this issue.

2. monitoring 2025-10-13 09:27 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 2025-10-13 11:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-02 17:39 UTC

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

2. identified 2025-09-02 19:42 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 2025-09-03 08:49 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 2025-09-03 17:03 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 2025-09-03 17:37 UTC

   We are continuing to monitor for any further issues.

6. resolved 2025-09-04 09:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-31 20:59 UTC

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

2. investigating 2025-07-31 21:01 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-07-31 21:19 UTC

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

4. resolved 2025-08-01 09:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-07-31 19:00 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.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-02 15:38 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 2025-07-04 10:11 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 2025-07-08 13:01 UTC

   We are still working to restore all affected rooms

4. identified 2025-07-11 09:46 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 2025-07-16 09:03 UTC

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

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-26 16:34 UTC

   We are currently investigating this issue.

2. identified 2025-06-26 16:49 UTC

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

3. monitoring 2025-06-26 19:02 UTC

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

4. resolved 2025-06-27 00:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-20 10:12 UTC

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

2. investigating 2025-06-20 10:12 UTC

   We are continuing to investigate this issue.

3. identified 2025-06-20 10:19 UTC

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

4. monitoring 2025-06-20 10:23 UTC

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

5. resolved 2025-06-20 10:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-20 03:21 UTC

   We are currently investigating this issue.

2. resolved 2025-06-20 04:01 UTC

   The database performance issue has now been identified and resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-20 12:00 UTC

   We are currently investigating this issue.

2. resolved 2025-05-20 14:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-26 15:37 UTC

   We are currently investigating the cause of this issue.

2. investigating 2025-03-26 15:37 UTC

   We are continuing to investigate this issue.

3. identified 2025-03-26 15:49 UTC

   We've identified the cause and are currently implementing a fix.

4. monitoring 2025-03-26 16:40 UTC

   A fix has been implemented and outbound federation appears to have returned.

5. resolved 2025-03-26 19:21 UTC

   Outbound federation is operational.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-02-26 09:42 UTC

   We are having issue with our email provider. No emails are being sent. Both registration and password reset are impacted.

2. identified 2025-02-26 09:44 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2025-02-26 12:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-04 11:43 UTC

   We are currently aware of an issue which is causing some issues with the creation of new devices in the Sliding Sync Proxy. Some users may find that clients such as Element X may never finish logging in or loading the home screen. Logging out and back in again may be sufficient...

2. resolved 2024-09-04 13:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-20 13:55 UTC

   Emails are currently not being delivered. This affects registration of new accounts and delivery of email notifications.

2. resolved 2024-08-23 07:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-24 17:36 UTC

   We are currently investigating this issue.

2. identified 2024-06-24 17:44 UTC

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

3. resolved 2024-06-24 17:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-24 15:38 UTC

   We are currently investigating this issue.

2. identified 2024-06-24 15:52 UTC

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

3. monitoring 2024-06-24 15:58 UTC

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

4. resolved 2024-06-24 16:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-14 10:48 UTC

   We are currently investigating this issue.

2. resolved 2024-06-14 11:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-06-11 19:42 UTC

   We are currently investigating an issue that started at approximately 18:50 UTC. This issue will mean that users won't be able to log in to new devices. Other functions of the homeserver appear to be working.

2. resolved 2024-06-11 19:57 UTC

   This issue has been resolved. Many thanks for your patience.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-10 19:34 UTC

   We are currently investigating this issue.

2. investigating 2024-06-10 19:38 UTC

   We are continuing to investigate this issue.

3. resolved 2024-06-10 19:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Outbound federation, OFTC IRC Bridge, Snoonet IRC Bridge, Slack, XMPP Bridge, W3C IRC Bridge, Torn IRC Bridge

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-06-08 12:56 UTC

   There is a backlog in the processing of events, meaning that outbound traffic to federation (other Matrix homeservers) and to Application Services (Bridges) at Matrix.org is delayed, by up to 20 minutes.

2. resolved 2024-06-08 13:40 UTC

   The backlog has been cleared. Thank you for your patience.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-06 13:57 UTC

   We are currently investigating this issue.

2. monitoring 2024-06-06 14:17 UTC

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

3. resolved 2024-06-06 15:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-05 15:41 UTC

   We are currently investigating this issue.

2. investigating 2024-06-05 16:05 UTC

   We are continuing to investigate this issue.

3. resolved 2024-06-05 17:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-05-17 15:18 UTC

   Performance of Matrix.org Synapse is currently degraded. We are aware of the cause and working on a remediation.

2. resolved 2024-05-18 16:41 UTC

   Performance of the Matrix.org homeserver has returned to normal.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-22 09:04 UTC

   The Matrix.org homeserver is currently failing to persist events, meaning users can't send events or receive them over federation We are working to remedy the problem.

2. investigating 2024-04-22 09:17 UTC

   The failure on Matrix.org has expanded and now users may be unable to sync (receive messages).

3. monitoring 2024-04-22 10:43 UTC

   The Matrix.org homeserver is running slowly, particularly when it comes to sending events, as it handles the backlog that built up whilst it was down.

4. investigating 2024-04-22 10:53 UTC

   The Matrix.org homeserver is once again inaccessible from clients. We are looking into the problem.

5. monitoring 2024-04-22 11:05 UTC

   The Matrix.org homeserver is now accessible from clients again. Event send performance is slightly degraded for the time being.

6. resolved 2024-04-22 12:32 UTC

   Performance seems to have recovered. Sorry for the trouble and thanks for your patience.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-03-26 22:10 UTC

   We've identified an issue with requests being timed out against matrix.org and are working to resolve it.

2. monitoring 2024-03-26 22:21 UTC

   A fix has been implemented and the system appears to have stabilised. We are currently monitoring the situation.

3. resolved 2024-03-27 15:45 UTC

   The system has been stable for a prolonged period of time and is considered resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-12-11 15:05 UTC

   We are currently aware of performance issues affected matrix.org local and federation traffic and are investigating.

2. identified 2023-12-11 15:15 UTC

   We've identified the issue and are working on a resolution.

3. resolved 2023-12-11 17:18 UTC

   Performance should be back to normal (for the time of day).

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-11-12 01:28 UTC

   We're investigating continued outages. Login and sending messages may not work in the meantime.

2. monitoring 2023-11-12 03:06 UTC

   The issue was fixed, which caused a large amount of outgoing federation traffic. This resulted in a similarly large influx of federation traffic, which our systems interpreted as a DDoS and cut inbound federation traffic. We've now allowed traffic to flow again, and currently...

3. resolved 2023-11-12 03:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-11-11 22:57 UTC

   We're aware of an issue with an issue on matrix.org Synapse and currently investigating.

2. resolved 2023-11-11 23:45 UTC

   The outage has been resolved after restarting the service. We are actively investigating the exact cause. As of now, normal service has been restored.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-11-08 17:58 UTC

   We are currently investigating degraded performance across matrix.org Synapse due to increased amounts of database traffic. Encrypted messages may be slow to decrypt as a result.

2. monitoring 2023-11-08 18:44 UTC

   We have identified the problem and have applied a fix. Now monitoring the situation to see whether it improves.

3. resolved 2023-11-08 23:47 UTC

   Service has been nominal over the last hour, and we're now confident that the issue has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-10-17 09:08 UTC

   We are currently investigating this issue.

2. resolved 2023-10-17 09:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-10-07 20:04 UTC

   We are currently investigating degraded performance of sending and receiving messages on matrix.org.

2. monitoring 2023-10-07 21:14 UTC

   We identified that the degraded performance was due to heavy E2EE-related federation traffic. Performance has stabilised and we are monitoring the situation.

3. resolved 2023-10-07 22:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2023-08-20 15:28 UTC

   Over the weekend matrix.org has been experiencing increased traffic, resulting in performance issues. While trying to mitigate this, a bug was introduced that caused issues with uploading keys for new devices, resulting in these new devices failing to receive encrypted messages....

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-08-05 14:00 UTC

   The Libera.Chat bridge will be disabled from 14:00 UTC on Saturday 5th August at the request of the Libera.Chat team. More details here https://matrix.org/blog/2023/08/libera-bridge-disabled/

2. resolved 2023-08-05 14:04 UTC

   The bridge is now disabled.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-04 00:00 UTC

   Messages are not making it between Matrix and IRC on the Libera.Chat bridge.

2. investigating 2023-08-04 09:59 UTC

   We are continuing to investigate this issue.

3. monitoring 2023-08-04 10:16 UTC

   We identified an issue with the proxy node for the bridge, which is now recovering

4. resolved 2023-08-05 12:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-08-01 08:45 UTC

   We're investigating instability with the bridge after yesterdays update.

2. monitoring 2023-08-01 15:05 UTC

   We've identified what we believe the root cause is and put in some monitoring to keep an eye on it.

3. monitoring 2023-08-01 15:15 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2023-08-01 15:23 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2023-08-01 15:26 UTC

   We are continuing to monitor for any further issues.

6. resolved 2023-08-02 08:33 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-07-14 03:00 UTC

   The matrix.org homeserver is currently experiencing problems with client and federation connections. We are investigating and will update on progress as we have it. Meanwhile, anyone using a server other than matrix.org is, of course, unaffected.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2023-06-14 14:07 UTC

   The bridge proxy process was unexpectedly restarted, and as a result will be nosily rejoining channels on IRC. The bridge should recover over the next hour.

2. resolved 2023-06-16 08:45 UTC

   This incident has been resolved. We're continuing to monitor the bridge.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-06-03 20:00 UTC

   We are aware of a problem preventing connections across the bridge. Updates will follow.

2. monitoring 2023-06-05 14:00 UTC

   We've updated the bridge with a version that should hopefully improve things. The team are continuing to monitor.

3. resolved 2023-06-06 19:36 UTC

   We've deployed some changes that seem to have helped. The bridge is continuing to be monitored.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-05-26 12:00 UTC

   High incidence of failed connections and dropped messages.

2. investigating 2023-06-01 07:00 UTC

   We've implemented a fix to solve a case where some Matrix users were not able to connect to IRC, and therefore prevented traffic being bridged.

3. investigating 2023-06-04 16:25 UTC

   We are continuing to investigate this issue.

4. resolved 2023-06-04 16:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse, Outbound federation

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-05-11 18:29 UTC

   We are currently investigating an issue where messages sent from matrix.org users are heavily delayed before reaching other homeservers.

2. monitoring 2023-05-11 19:25 UTC

   Outbound federation has returned to normal and we are monitoring for further issues.

3. resolved 2023-05-12 09:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Affected: Synapse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-05-10 16:27 UTC

   We are currently investigating a performance issue when sending messages that started at 15:24 UTC.

2. resolved 2023-05-10 19:23 UTC

   We have identified the source of the performance issues when sending messages and applied mitigations to return performance to normal.

Excerpts are shortened. Read the full incident on Matrix.org's status page.

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2023-05-10 10:07 UTC

   Maintenance is taking a bit longer, messages may be delayed or missed for the next few hours. We'll update as we find out more.

2. resolved 2023-05-10 14:15 UTC

   The bridge is now up and running on new infra, we're continuing to monitor.

Excerpts are shortened. Read the full incident on Matrix.org's status page.