Network World reported the second of two serious outages at IBM Cloud within a week.
This outage took about four hours to resolve:
"Once again, IBM Cloud users were locked out, unable to log in via the console, the CLI, or the API. The incident resulted in customers being unable to manage or provision essential cloud resources. Furthermore, the incident caused IAM authentication failures and even disrupted access to the support portal, making it impossible to open or track support cases."
Network World quotes analyst Manish Rawat at TechInsights, who speculates on the root causes of the outage. Rawat suggested that “. . . repeated security and availability issues in IBM Cloud suggest deeper flaws in its security architecture and incident response protocols. The recurrence points to unresolved root causes and possible gaps in resilience design, such as inadequate failover systems and weak infrastructure segmentation."
Of more serious concern, another analyst suggests, is that this reflects a systemic problem with massive cloud providers. Sanchit Vir Gogia at Greyhound Research, quoted in the same story, worries that:
“The recent IBM Cloud outages are part of a broader pattern of modern cloud dependencies being over-consolidated, under-observed, and poorly decoupled. Most enterprises — and regulators — tend to scrutinise cloud strategies through the lens of data sovereignty, compute availability, and regional storage compliance. Yet it is often the non-data-plane services—identity resolution, DNS routing, orchestration control — that introduce systemic exposure."
Not to mention the impact of specialization and complexity.
No comments:
Post a Comment