IBM Cloud resets ‘Days Since Last Major Incident’ clock to zero – after just five days
Sixth big outage in seven weeks, this time users were unable to access more than a dozen services Share
Copy
IBM’s Cloud is experiencing another severity-one issue, the rank it uses for incidents that see business-critical systems become unavailable.
“Users may experience connectivity issues when trying to access the listed cloud services” was the explanation offered when the incident kicked off at 1454 UTC on May 25. Resources in Washington DC, Osaka, London, Dallas, Sydney, Tokyo, and Frankfurt were all impacted.
Those cloud services were: App ID; Cloudant NoSQL DB; Code Engine; Continuous Delivery; Toolchain; DNS Services; Event Streams; Hyper Protect Crypto Services; Hyper Protect Virtual Server; Hyper Protect DBaaS; IBM Cloud Shell; IBM Watson Machine Learning; Mobile Foundation; and MQ in IBM Cloud. IBM’s most recent status update available at the time of writing,
As more and more businesses move to a hybrid cloud model it poses a challenge for developers who need to manage the complexities of the infrastructure alongside coding.