Skip to main content

Is IBM Cloud Down?

No — IBM Cloud is up

Reachable from all 8 checked regions

Average response time: 578ms

Last checked · checks run every 6 hours

Official status page: https://cloud.ibm.com/status

IBM Cloud uptime

100%
Last 7 days
—
Last 30 days
—
Last 90 days
—
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 6 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

6-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: 100.00% uptime, 29 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 24 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
217ms
DNS 0ms TCP 2ms TLS 5ms TTFB 209ms
arn
136ms
DNS 0ms TCP 0ms TLS 2ms TTFB 126ms
bom
1047ms
DNS 0ms TCP 2ms TLS 5ms TTFB 1036ms
cdg
200ms
DNS 0ms TCP 1ms TLS 4ms TTFB 193ms
dfw
489ms
DNS 0ms TCP 21ms TLS 46ms TTFB 403ms
ewr
476ms
DNS 0ms TCP 2ms TLS 6ms TTFB 467ms
fra
1482ms
DNS 1ms TCP 100ms TLS 203ms TTFB 1093ms
gru
578ms
DNS 0ms TCP 2ms TLS 5ms TTFB 568ms
yyz
666ms
DNS 1ms TCP 0ms TLS 3ms TTFB 658ms

What IBM Cloud does

IBM Cloud is an enterprise platform for running applications across hybrid and multicloud environments, combining infrastructure, platform services, AI and automation with compliance controls aimed at regulated industries. Banks, insurers and public sector bodies run mission-critical workloads on it, often alongside on-premises systems, so an incident tends to surface inside internal applications rather than on a consumer website.

What an outage looks like

Provisioning fails or hangs while already-running instances keep serving, which is the usual shape of a control-plane incident. The IBM Cloud console will not load or times out on login. API and CLI calls return 5xx. Because IBM Cloud is organised by region and zone, one location can fail while workloads in another run untouched, so check where the affected service is deployed.

What to do about it

cloud.ibm.com/status carries unplanned incidents, planned maintenance, announcements and security bulletins, with write-ups at cloud.ibm.com/status/incident-reports. Filter to the services and regions you actually use, since the platform is wide and most entries will not apply. Hold off on redeploying during a control-plane incident: new provisioning is often the failing part while running workloads are fine.

Is it down for everyone, or just you?

If this page says IBM Cloud is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

AWS
AWS
O
Oracle Cloud
L
Linode
DigitalOcean
DigitalOcean

IBM Cloud outage FAQ

Are my running workloads affected during an IBM Cloud incident?
Often not. Many cloud incidents hit the control plane, meaning the console, APIs and provisioning, while instances already running continue to serve traffic. Check whether the reported service is one your application calls at runtime or only one you use to deploy. If it is the latter, the safest action during the incident is to change nothing.
Is IBM Cloud down globally or in one region?
Usually one region or zone. IBM Cloud is deployed across regions and availability zones, and the status page identifies which location an incident affects. A workload in Frankfurt can be untouched while Dallas is degraded. Confirm where your services are actually deployed before responding, since most entries on a large platform's status page will not apply to you.
Where do I find the write-up after an IBM Cloud outage?
cloud.ibm.com/status/incident-reports carries incident reports, and the announcements section covers planned changes. These are the documents to quote in an internal post-mortem or to a customer asking why a service was unavailable, since a screenshot of a status banner rarely satisfies either audience for long.
Does an IBM Cloud outage affect IBM's other products?
Not necessarily. IBM Cloud is the platform for infrastructure and platform services, and other IBM offerings can run elsewhere or report through their own channels; IBM Security publishes a separate status page. Match the specific service your team depends on rather than treating everything carrying the IBM name as one system.

How we measure this

  • We request IBM Cloud's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where IBM Cloud publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when IBM Cloud goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required