Matrix Outage History
10 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Matrix Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 26, 2026 | Machines maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Aug 3, 2026 | Matrix.org Homeserver: Degraded performanceThis incident has been resolved. | 11h 26m | Resolved |
| May 5, 2026 | Performance degradationAround 07:00 UTC until 08:00 UTC, performance on the matrix.org homeserver was degraded due to a transient problem preventing database maintenance. | 0 min | Resolved |
| Apr 16, 2026 | Problems sending messages via matrix.orgThe homeserver has been stable since rolling back. The Synapse team will work on a resolution to the bug that caused the outage. | 7h 9m | Resolved |
| Mar 19, 2026 | Slow outbound federationThis incident has been resolved. | 23 min | Resolved |
| Mar 2, 2026 | Performance of sending and loading messages is degradedThis incident has been resolved. | 39h 39m | Resolved |
| Mar 2, 2026 | Performance issues regarding message sending on matrix.orgThis incident has been resolved. | 3h 13m | Resolved |
| Mar 2, 2026 | Sending messages has reduced performanceThis incident has been resolved. | 3h 17m | Resolved |
| Feb 24, 2026 | Slow loginsThis incident has been resolved. | 3h 13m | Resolved |
| Feb 11, 2026 | Degraded performanceThis incident has been resolved. | 10h 37m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Matrix incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Matrix Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Matrix acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Matrix outage in this window ran 1d 15h, against a mean recovery of 7h 60m. If you depend on Matrix in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.