Live / CloudSigma / Incident
CloudSigma: [ALL] Chat & Ticketing System Unavailable
CloudSigma · cloudsigma.comMajor incidentinvestigating2026-10-18 13:03 UTC
Public — what happened
Summary
CloudSigma said its chat and ticketing systems became unavailable starting 2026-09-28 at 07:11 UTC, and that it could not accept chats at that point. By 2026-09-30 it reported chat was working again, but tickets still could not be opened from the WebApp. The company said chat went down again on 2026-10-15 and 2026-10-18 and was restored each time within hours, while the ticketing problem was still being worked on. CloudSigma has not named a cause, the incident is still marked as investigating, and it said customers can email [email protected] for urgent requests.
Affected
Zürich Cloud, Geneva Cloud, Frankfurt Cloud, Dusseldorf Cloud, Dublin Cloud, Washington DC Cloud, Monterrey Cloud, Perth Cloud, Riyadh Cloud, Tokyo Cloud, Manila Cloud, Manila 2 Cloud, Clark Cloud, Johor Bahru Cloud, Cairo cloud
Timeline
- Started — 2026-09-28 07:11 UTC
- Investigating — 2026-09-28 07:11 UTC (6 updates)
- Ongoing at last check.
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 41, 2026, our weekly internet health report.