IBM Cloud has taken time off – 23 services were difficult to provision for eight hours • The Register



IBM’s cloud experienced a major Severity 1 outage – the rating Big Blue uses to designate the most serious incidents that make its cloud resources unavailable to customers.

The impact was indeed severe: IBM said that users might not be able to access its catalog of cloud services or provide the affected services.

Speaking of which, there were 23 – among them Cloud Object Storage, Block Storage Snapshots for VPC, Load Balancers, and Virtual Private Networks. In other words, some of the basic building blocks of enterprise computing that clouds are supposed to be able to scale up as you (or your infrastructure as code) need more resources.

Emails sent to IBM customers and to the company’s Incident Customer Portal offered different timeframes for the incident. The emails say 4:41 p.m. UTC on August 2 as IBM began investigating the issue, but the portal’s first listed action is an ongoing investigation at 8:56 p.m. The timelines converge at 9:24 p.m. when the mitigation began, before resolution at 12:54 a.m. on August 3.

IBM’s cloud suffered a similar outage on Sunday, and some of the services that could not be delivered over the weekend were also down today. Big Blue’s Cloud Console was among the casualties over the weekend.

IBM also experienced an outage on July 22 when users were unable to connect to its cloud, and experienced similar outages on April 3, April 26 and May 31. The company said The register the July outage was due to the temporary demise of Akamai’s DNS Edge.

In June 2020, IBM’s cloud fell so hard that even its self-hosted status page was unavailable. The register asked IBM if it is working to ensure that its cloud does not suffer from single points of failure, whether at Akamai, internally, or elsewhere.

The company did not answer our questions.

The result is that IBM was twice unable in two days to present its cloud catalog to users or ensure that they can provide all services.

Yes, the same IBM who bet their business on hybrid clouds.

IBM isn’t the only one having big problems, however.

Google Cloud has also experienced blackouts in recent days. The company’s Component Access Gateway produced errors for nearly two days, and last week, users experienced three days and ten hours of issues in which it was unreliable to provision SSDs. persistent in four US-based regions. This meant that users couldn’t create new resources in Google Compute Engine, Google Kubernetes Engine, Cloud Composer, Cloud SQL, Cloud Dataproc, and Apigee X.

Again, this is not at all the “what you need, when you need it” experience promised by elastic public clouds. ®


Leave A Reply

Your email address will not be published.