cside Outage History
9 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 cside Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 6, 2026 | Dashboard and API are down.Resolved | 49 min | Resolved |
| Jul 30, 2026 | Degradation of proxyAll operational | 2h 3m | Resolved |
| Jun 16, 2026 | A subset of cside customers were impacted by a subrequest failure. Impacted parties have been contactedA subset of cside customers were impacted by a subrequest failure. Impacted parties have been contacted | -1443 min | Resolved |
| May 28, 2026 | Dashboard is downThe issue was resolved | 42 min | Resolved |
| May 14, 2026 | Increased API latencyThe issue has been resolved | 1h 12m | Resolved |
| Apr 15, 2026 | Dashboard Authentication unavailableThe resolution was deployed and further preventative actions scoped. | 5 min | Resolved |
| Apr 1, 2026 | Dashboard temporarily unavailableDashboard fully operational now. | 11 min | Resolved |
| Feb 6, 2026 | Dashboard temporarily unavailableDashboard is healthy again | 1h 0m | Resolved |
| Nov 18, 2025 | Outage due to cloudflare incidentThe incident with cloudflare has now been resolved and all functionality to our API and dashboard services are fully functional. | 5h 34m | 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 cside 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 cside 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 cside 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 cside outage in this window ran 5h 34m, against a mean recovery of 1h 27m. If you depend on cside 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.