Live / Cloudways / Incident
Cloudways: Autonomous: Partial Service Degradation – London Region
Cloudways · cloudways.comCritical outageResolved2026-10-21 07:15 UTC
Public — what happened
Summary
Cloudways said that some of its Autonomous applications hosted in the London region may have had temporary connectivity problems, starting at 07:29 UTC on 2026-10-20 and describing it as a partial disruption. By 10:05 UTC the company said it had identified the problem as coming from its upstream provider in London, and that it was coordinating with that provider's team on a fix. The incident was later marked resolved at 07:15 UTC on 2026-10-21.
Timeline
- Started — 2026-10-20 07:29 UTC
- Investigating — 2026-10-20 07:29 UTC
- Identified — 2026-10-20 10:05 UTC
- Resolved — 2026-10-21 07:15 UTC · 23h 46m 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 Cloudways 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 Cloudways: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Cloudways report →
More from Cloudways
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.