# Business Continuity Published articles for Business Continuity. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Azure East US outage exposed shared infrastructure risks across major AI services DevFeed: [Azure East US outage exposed shared infrastructure risks across major AI services]() Original publisher: [Read original article]() Author: David Linthicum Published: 2026-09-18T09:00:00Z Content type: opinion Language: en Sources: [InfoWorld]() Topics: [Azure](), [Cloud](), [cloud-infrastructure](), [Risk](), [Artificial Intelligence](), [ChatGPT](), [Claude](), [Microsoft](), [OpenAI]() Tags: [ai](), [artificial-intelligence](), [artificial-intelligence-business-continuity-cloud-computing-generative-ai-saas](), [azure](), [business-continuity](), [chatgpt](), [claude](), [cloud](), [cloud-computing](), [generative-ai](), [infrastructure](), [microsoft](), [openai](), [outage](), [risk](), [saas]() ### AI overview An Azure East US failure degraded ChatGPT, Claude, Grok, and Copilot at nearly the same time. The article argues that shared cloud dependencies create concentrated risk for AI services and enterprise systems. ### Source excerpt September 3 started like any other Thursday, until it didn't. Within roughly 90 minutes, ChatGPT, Claude, Grok, and even Microsoft's own Copilot were degraded or dark, knocked sideways by a failure in Microsoft Azure's East US region. Downdetector logged more than 37,000 reports for ChatGPT alone, more than 1,300 for Claude, and roughly 1,365 for Grok. OpenAI's status page flagged elevated errors across 15 ChatGPT components and four Codex components, and by the time engineers had mitigations in place, combined report counts had climbed past 66,000. What made this event remarkable was not the scale of any single outage, but its simultaneity. Three aggressively competing AI labs--OpenAI, Anthropic, and xAI--each spend billions differentiating their models, yet all three buckled at nearly the same moment because they shared the same regional dependency. Gemini, notably, stayed largely upright because Google runs its flagship assistant on its own vertically integrated cloud. The outage that took down its rivals had no attack surface inside Google's stack. That's not luck; that's architecture. The lesson buried in the details of that morning is this: A single cloud region became unhealthy, and four of the most prominent AI services on the planet, owned by four different companies, fell over together. Copilot's involvement is perhaps the most telling data point. Microsoft's own first-party assistant runs on Microsoft's own cloud, and it still had a rough morning. When the house itself shakes, you know the failure sits deep in shared infrastructure layers, not in any tenant's configuration. This is not an "AI is unreliable" story. This is a concentrated risk story, and every enterprise architect should be re-examining their own dependency maps this week. A fast-growing blast radius Here is the part that should genuinely change how you think. These were consumer-facing chatbots having a bad morning. Now extend the same failure pattern six months forward, when enterprise larg ## NetApp and Veeam Advancing Data Resilience Together DevFeed: [NetApp and Veeam Advancing Data Resilience Together]() Original publisher: [Read original article]() Author: Pete Ybarra Published: 2026-09-16T15:00:00Z Content type: article Language: en Sources: [Veeam Software Official Blog]() Topics: [Resilience](), [backups](), [Disaster Recovery](), [ransomware](), [Replication](), [REST API](), [Cloud]() Tags: [alliance-partners](), [api](), [backup](), [backups](), [business](), [business-continuity](), [cloud](), [engineering](), [netapp](), [ontap](), [ransomware](), [ransomware-resilience](), [resilience](), [storage-integration]() ### AI overview The article describes the NetApp USAPI 2.1 Plug-in for Veeam Data Platform, a REST-based ONTAP integration intended to simplify snapshot management, replication, disaster recovery, ransomware protection, and adoption of new capabilities. It also discusses portable backups for moving workloads between hypervisor platforms. ### Source excerpt Every organization now runs on data it cannot afford to lose. As data estates expand and cyber risk grows, resilience strategies must simplify operations, reduce risk, and protect business continuity. Ransomware, outages, cloud migrations, and hypervisor changes all raise the stakes, but many storage and backup integrations are thin partnerships assembled after the fact. Veeam and NetApp are different. The post NetApp and Veeam Advancing Data Resilience Together appeared first on Veeam Software Official Blog. ## Claude outage, June 2026: Reckoning with AI's increasing status as infrastructure DevFeed: [Claude outage, June 2026: Reckoning with AI's increasing status as infrastructure]() Original publisher: [Read original article]() Author: Ken Mugrage Published: 2026-06-03T00:00:00Z Content type: article Language: en Sources: [Thoughtworks Insights]() Topics: [Claude](), [anthropic](), [incident](), [Artificial Intelligence](), [Large Language Model](), [Resilience](), [Availability](), [Claude Code](), [API](), [cloud-infrastructure]() Tags: [ai](), [ai-tools](), [anthropic](), [availability](), [business-continuity](), [claude](), [claude-code](), [cli](), [data](), [database](), [downtime](), [engineering](), [incident-response](), [outage](), [status]() ### AI overview The article examines Anthropic's June 2, 2026 Claude outage, which affected Claude models, the Claude API, and Claude Code. It argues that widespread reliance on generative AI makes provider outages a resilience and business-continuity concern, and discusses the risks of depending on a single vendor. ### Source excerpt Claude outage, June 2026: Reckoning with AI's increasing status as infrastructure ## After CrowdStrike: Navigating the path to digital resilience DevFeed: [After CrowdStrike: Navigating the path to digital resilience]() Original publisher: [Read original article]() Author: Jim Gumbley Published: 2024-07-26T00:00:00Z Content type: opinion Language: en Sources: [Thoughtworks Insights]() Topics: [Resilience](), [distributed-systems](), [Risk](), [Cybersecurity](), [Disaster Recovery](), [data](), [Users]() Tags: [business-continuity](), [cybersecurity](), [data](), [dependencies](), [devices](), [digital-resilience](), [disaster-recovery](), [distributed-systems](), [resilience](), [risk]() ### AI overview The CrowdStrike disruption illustrates why failures in complex, interconnected software systems are inevitable. The article argues that digital resilience depends on modeling digital assets and relationships, applying targeted technology controls, and preparing to minimize the impact of incidents. ### Source excerpt After CrowdStrike: Navigating the path to digital resilience