Live  /  Providers  /  IBM Cloud

IBM Cloud

ibmcloud.comNo open incidents

Independent assessment — SquidGrid is not affiliated with IBM Cloud. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Cloud & hosting · SquidGrid tracks IBM Cloud’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what IBM Cloud is reporting

Current & recent incidents

Resolved

IBM Cloud: Data Center Power Infrastructure (ams03)

Critical impact · 2026-06-28 20:00 UTC

Resolved

IBM Cloud: Compute General (ams03)

Major impact · 2026-06-09 21:00 UTC

Resolved

IBM Cloud: Cloudant (ams03)

Major impact · 2026-06-05 16:00 UTC

Resolved

IBM Cloud: Cloud Object Storage (ams03)

Critical impact · 2026-05-25 19:00 UTC

Resolved

IBM Cloud: File Storage for Classic (ams03)

Major impact · 2026-05-25 16:00 UTC

Resolved

IBM Cloud: Kubernetes Service (ams03)

Critical impact · 2026-05-25 16:00 UTC

Resolved

IBM Cloud: Db2 (ams03)

Critical impact · 2026-05-25 16:00 UTC

Resolved

IBM Cloud: Cloud Load Balancer (ams03)

Major impact · 2026-05-25 16:00 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what IBM Cloud has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

IBM Cloud runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of IBM Cloud is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with IBM Cloud.