Quorum Outage History
4 incidents recorded over the last 365 days, 4 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 Quorum Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Quorum Service InterruptionThis incident has been resolved. | 13h 55m | Resolved |
| Sep 16, 2026 | Quorum Service InterruptionThis incident has been resolved. | 32 min | Resolved |
| Aug 13, 2026 | Elevated API ErrorsThis incident has been resolved. | 2h 40m | Resolved |
| Aug 5, 2026 | Media alerts are delayedThe issue has been resolved, and the data backfill has completed. According to our service provider, a small amount of content may not be recoverable if it was removed or moved from the original source while the… | 289h 0m | 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 Quorum 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 Quorum 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 Quorum 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 Quorum outage in this window ran 12d 1h, against a mean recovery of 3d 4h. If you depend on Quorum 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.