Live / CloudSigma / Incident
CloudSigma: [MNL2] Unavailable hosts
CloudSigma · cloudsigma.comMajor incidentResolved2026-10-10 08:31 UTC
Public — what happened
Summary
CloudSigma reported a major issue starting at 04:07 UTC on 2026-10-10 involving some compute hosts in its Manila 2 cloud location. The company said virtual machines kept running but could appear as unavailable, which might block customers from starting, stopping or cloning them. At 06:28 UTC CloudSigma said it had traced the problem to a power outage and had a team on site working to bring power back. The incident was marked resolved at 08:31.
Affected
Manila 2 Cloud
Timeline
- Started — 2026-10-10 04:07 UTC
- Investigating — 2026-10-10 04:07 UTC (2 updates)
- Identified — 2026-10-10 06:28 UTC
- Resolved — 2026-10-10 08:31 UTC · 4h 24m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach CloudSigma against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for CloudSigma: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the CloudSigma report →
More from CloudSigma
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.