IBM Cloud Outage History
2 incidents recorded over the last 365 days, 2 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded IBM Cloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 6, 2025 | IBM Cloud Red Hat Openshift AI Addon is affected by a security vulnerability (CVE-2025-10725)IBM Cloud Red Hat Openshift AI Addon is affected by a security vulnerability in the Red Hat Openshift AI operator ( CVE-2025-10725 ). The fix will be applied to customers' clusters automatically, if the customer has… | — | Investigating |
| Sep 24, 2025 | IBM Cloud Kubernetes Service is affected by a Kubernetes API server security vulnerability (CVE-2025-5187)IBM Cloud Kubernetes Service is affected by a security vulnerability in the Kubernetes API server that may allow node users to delete their corresponding node object by patching themselves with an OwnerReference to a… | — | Investigating |
How to Read This IBM Cloud Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before IBM Cloud acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.