Operations | Monitoring | ITSM | DevOps | Cloud

In a single week, two of the largest cloud providers on earth failed at almost the same time, and a good chunk of the internet went with them. Effective cloud outage response stopped being a theoretical exercise and became the difference between a calm 30 minutes and a chaotic afternoon for thousands of on-call engineers. On July 23, 2026, a maintenance bug inside Microsoft Azure pulled IP routes off more devices than intended in the West US region, cutting Microsoft 365 access for millions.

IncidentHub's latest product update includes a Multi-client plan built specifically for MSPs and agencies with per-client status pages, service components as top-level objects on status pages, and support for more vendors (1125+ and counting).

Cloud outage response got another live fire drill on July 24, 2026, when AWS lost network connectivity between its us-west-2 region in Oregon and the Seattle metro. For most customers the pain lasted about 20 minutes, and a small set on AWS Direct Connect saw errors for roughly an hour and seventeen minutes. That is short as major cloud incidents go. What makes it worth your attention is not the duration.

On the morning of July 24, 2026, a large slice of the internet blinked out at once. An AWS outage centered on the US-West-2 region in Oregon rippled outward and took DoorDash, Reddit, Hulu, Apple Pay, Snapchat, Fortnite, and the PlayStation Network offline for millions of users. If your team runs anything on Amazon Web Services, this is the incident to study, because the hard part was never fixing AWS. The hard part was AWS outage incident response.

On July 24, 2026, AWS lost connectivity between the us-west-2 (Oregon) region and the Seattle Metro. The initial impact window was 20 minutes for most and 1 hour 17 minutes for a few customers using AWS Direct Connect through EqSe2, Westin Building Exchange, Seattle. Any traffic that both started and ended inside the region kept working, whereas anything crossing the region boundary saw timeouts and errors. This included the AWS Management Console for some customers.

On July 23, 2026, Azure users around the world began hitting gateway timeouts, DNS failures, and unreachable virtual machines well before Microsoft posted anything on its status page. The first reports reached StatusGator at 15:06 UTC. By 15:28 UTC, StatusGator had sent an Early Warning Signal to subscribers. Microsoft did not acknowledge the incident until 16:29 UTC.

On July 23, 2026, Microsoft Azure experienced a connectivity outage in the West US region that blocked traffic entering or leaving the region for nearly five hours. Workloads that stayed entirely inside West US were not affected. Microsoft's preliminary Post Incident Review (PIR) attributes the failure to a bug in maintenance request conversion software that removed IP routes from more devices than intended during routine device maintenance.