StatusCake Outage History
1 incident recorded over the last 365 days, 1 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 StatusCake Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 18, 2025 | Cloudflare outageCloudflare have communicated that a fix has been implemented. They believe the incident is now resolved. On the StatusCake side we are no longer seeing disruption. We can conclude that our alerting, API and reporting… | 2h 55m | Resolved |
How to Read This StatusCake 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 StatusCake 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 StatusCake outage in this window ran 2h 55m, against a mean recovery of 2h 55m. If you depend on StatusCake 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.