IBM Cloud has encountered two significant Severity One incidents within a fortnight, preventing users from logging in. The first incident occurred on May 21, affecting 15 products including key services like Kubernetes. The second incident on June 2 escalated impacts to 41 products. Both incidents highlighted issues with IAM authentication and access to resources, with conflicting information in IBM's status reports further complicating user understanding of the outages' timelines and causes. Customers have reported serious disruptions in managing their cloud infrastructures during these incidents.
IBM's Cloud has faced two severe login outages in just over two weeks, affecting user access to critical cloud services.
The first incident on May 21 affected 15 products, while the second on June 2 impacted 41 products.
Conflicting information in IBM's status report makes it difficult to determine the actual timeline and resolution steps for the incidents.
Customers have been unable to manage their cloud resources, leading to significant operational challenges and service interruption.
Collection
[
|
...
]