Element Outage History
11 incidents recorded over the last 365 days, 3 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 Element Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 9, 2026 | EMS infrastructure maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 11, 2026 | EMS infrastructure maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 27, 2026 | Issue with Gitter login methodsThis incident has been resolved. | 1h 10m | Resolved |
| Apr 9, 2026 | Element Call scheduled maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Apr 2, 2026 | Gitter scheduled maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Mar 25, 2026 | Element One scheduled maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Mar 12, 2026 | EMS infrastructure maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 19, 2026 | Customer portal and image registry scheduled maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 5, 2025 | Helm Registry registry.element.io/helm access issuesThis incident has been resolved. | 2h 10m | Resolved |
| Nov 18, 2025 | Issues at CloudFlare causing widespread outages in EMSThis incident has been resolved. | 18h 17m | Resolved |
| Nov 12, 2025 | Element One migration to next-generation authentication for Element X supportThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
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 Element 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 Element 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 Element 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 Element outage in this window ran 18h 17m, against a mean recovery of 2h 33m. If you depend on Element 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.