Live / IBM Cloud / Incident
IBM Cloud: IBM Cloud: IBM Cloud (us-east, jp-osa, br-sao, eu-gb, us-south, au-syd, in-che, ca-tor, jp-tok, eu-de, eu-es, ca-mon, in-mum)
IBM Cloud · ibmcloud.comCritical outageResolved2026-11-10 14:17 UTC
Public — what happened
Summary
IBM Cloud said it is carrying out emergency maintenance, which began around 15:05 UTC on 2026-10-21 and affects many regions. The company said existing production workloads on VPC and Classic are not expected to be affected, but people may be unable to create new Classic resources or change existing ones. IBM Cloud said that VPC provisioning problems were mitigated by 17:00 UTC, leaving only the Classic limits. In its latest update at 20:40 UTC, it said it aims to restore Classic provisioning within 8 hours, and the incident is not yet marked resolved.
Timeline
- Started — 2026-10-21 15:05 UTC
- Resolved — 2026-10-22 15:00 UTC · 23h 55m 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 IBM Cloud 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 IBM Cloud: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the IBM Cloud report →
More from IBM Cloud
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.