Cloudcone Outage History
7 incidents recorded over the last 365 days, 7 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 Cloudcone Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Scheduled Maintenance – Emergency patch for all VPS / SC2 Nodes | 9h 59m | Resolved |
| Oct 21, 2026 | Scheduled Maintenance - PHP Update | 1h 41m | Resolved |
| Sep 29, 2026 | Service Outage | 3h 3m | Resolved |
| Sep 26, 2026 | RAID Maintenance on S190-V | 23h 11m | Resolved |
| Sep 9, 2026 | Scheduled Maintenance – St. Louis (STL) Hypervisors | 47 min | Resolved |
| Sep 6, 2026 | Hypervisor Outage | 12h 6m | Resolved |
| Jul 23, 2026 | SC2 Backup & Snapshot Creation Temporarily Disabled | 1037h 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 Cloudcone 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 Cloudcone 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 Cloudcone 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 Cloudcone outage in this window ran 43d 5h, against a mean recovery of 6d 11h. If you depend on Cloudcone 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.