Live / IBM Cloud / Incident
IBM Cloud: IBM Cloud: Data Center Power Infrastructure (ams03)
IBM Cloud · ibmcloud.comCritical outageResolved2026-06-28 20:00 UTC
Public — what happened
Summary
IBM Cloud said a fire broke out at 06:33 UTC on 7 May 2026 at its AMS03 data center in Amsterdam, a facility run by the independent provider NorthC, and the resulting loss of power took all equipment there offline, cutting customers off from IBM Cloud services hosted at the site. The company said restoring service required relocating equipment to other server rooms in the building and reconfiguring its control systems, and it handled recovery client by client, holding environments for customers who asked by 12 May 2026, 17:30 UTC. IBM Cloud reported on 15 May 2026 that access had been restored and customers could again reach and create resources in AMS03. It added that NorthC had indicated the fire was not the result of malicious activity.
Timeline
- Started — 2026-05-07 06:33 UTC
- Resolved — 2026-05-15 14:00 UTC · 8 days 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
- IBM Cloud: IBM Cloud (us-east, jp-osa, br-sao, eu-gb, us-south, au-syd, in-che, ca-tor, jp 2026-10-21
- IBM Cloud: Classic Infrastructure Provisioning (us-east, jp-osa, br-sao, eu-gb, us-south, 2026-10-21
- IBM Cloud: Cloud Object Storage (ams03) 2026-05-07
- IBM Cloud: Compute General (ams03) 2026-05-07
- IBM Cloud: Cloudant (ams03) 2026-05-07