Discourse Outage History
13 incidents recorded over the last 365 days. 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 Discourse Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 20, 2026 | Brief read only during maintenanceScheduled Maintenance | 5h 0m | Scheduled |
| Oct 18, 2026 | Brief read only during maintenanceScheduled Maintenance | 8h 0m | Scheduled |
| Oct 15, 2026 | Brief read only during maintenanceScheduled Maintenance | 9h 0m | Scheduled |
| Sep 29, 2026 | Brief read only during maintenanceScheduled Maintenance | 8h 0m | Scheduled |
| Sep 28, 2026 | Brief read only during maintenanceScheduled Maintenance | 8h 0m | Scheduled |
| Sep 27, 2026 | Brief read only during maintenanceScheduled Maintenance | 8h 0m | Scheduled |
| Sep 25, 2026 | Brief read only during maintenanceScheduled Maintenance | 5h 0m | Scheduled |
| Sep 24, 2026 | Brief read only during maintenanceScheduled Maintenance | 3h 30m | Scheduled |
| Sep 23, 2026 | Brief service interruption during maintenanceScheduled Maintenance | 1h 0m | Scheduled |
| Aug 14, 2026 | Brief read only during maintenanceScheduled Maintenance | 1h 0m | Scheduled |
| Aug 13, 2026 | Brief read only during maintenanceScheduled Maintenance | 4h 0m | Scheduled |
| Aug 11, 2026 | Brief read only during maintenanceScheduled Maintenance | 2h 0m | Scheduled |
| Aug 10, 2026 | Brief read only during maintenanceScheduled Maintenance | 5h 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 Discourse 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 Discourse 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 Discourse 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 Discourse outage in this window ran 9h, against a mean recovery of 5h 12m. If you depend on Discourse 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.