# Cloud & SaaS Outage Postmortems | RuntimeHQ

* **Canonical URL:** https://theruntimehq.com/outages
* **Markdown Index URL:** https://theruntimehq.com/outages.md
* **Total Postmortems:** 5
* **Last Updated:** 2026-11-21

**Summary:** Primary-source architectural postmortems analyzing major cloud, identity, payment, and SaaS outages through the lens of downstream client-runtime resilience and capability-scoped Operational State.

---

## Comparative Outage Matrix

| Incident Date (UTC) | Provider | Verified Duration | Failure Pattern | Client-Side Operational Gap | Primary Source | Analysis |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- |
| 2026-11-17 | Apple Services | ~3h 40m (82m status lag) | Federated Rail Asymmetry | Apple Pay and Sign in with Apple degraded alongside operational card and Google rails while official status acknowledgement lagged by 82 to 88 minutes. | [Stripe & Claude Status Disclosures](https://status.stripe.com/) | [HTML](https://theruntimehq.com/insights/19-apple-november-2026-outage-federated-auth-payment-rails) / [MD](https://theruntimehq.com/insights/19-apple-november-2026-outage-federated-auth-payment-rails.md) |
| 2026-11-12 | Microsoft 365 | ~24h core (~44h envelope) | Ecosystem Connector Cascade | Tenant-bound Exchange and Graph dependencies prevented transparent multi-cloud failover, prolonging impairment inside downstream AI connectors and public portals. | [Microsoft Service Health (EX1550543 / MO1550821)](https://status.cloud.microsoft/) | [HTML](https://theruntimehq.com/insights/18-microsoft-365-november-2026-outage-connector-cascades) / [MD](https://theruntimehq.com/insights/18-microsoft-365-november-2026-outage-connector-cascades.md) |
| 2026-10-20 | Google Cloud | 6h 10m core (8h 10m total) | Cross-Zone Failure Cascade | A single-zone power loss in europe-west2-b spilled into surviving London zones via failover compute surges and synchronous cross-zone control-plane timeouts. | [Google Cloud Incident Report](https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj) | [HTML](https://theruntimehq.com/insights/15-google-cloud-london-outage-cross-zone-cascades) / [MD](https://theruntimehq.com/insights/15-google-cloud-london-outage-cross-zone-cascades.md) |
| 2026-09-30 | Microsoft Azure | 5h 45m | Ingress & Management Plane Coupling | Multi-region gateway connectivity and management plane degradation constrained remote configuration pushes and emergency deployment pipelines. | [Azure Status History](https://azure.status.microsoft/en-us/status/history/) | [HTML](https://theruntimehq.com/insights/12-azure-outage-postmortem-ingress-gateway-failure) / [MD](https://theruntimehq.com/insights/12-azure-outage-postmortem-ingress-gateway-failure.md) |
| 2026-09-16 | Salesforce | 7h 36m | In-Band Dependency Coupling | Help portal and support intake shared the degraded Hyperforce login tier, stalling customer case creation across 7 hours and 36 minutes of mitigation. | [Salesforce Incident 20004433](https://status.salesforce.com/incidents/20004433) | [HTML](https://theruntimehq.com/insights/10-salesforce-outage-postmortem-the-in-band-dependency-trap) / [MD](https://theruntimehq.com/insights/10-salesforce-outage-postmortem-the-in-band-dependency-trap.md) |

---

## Published Outage Postmortems

### Apple Outage: Isolating Federated Auth and Payment Rails
- **Provider:** Apple Services
- **Incident Date (UTC):** 2026-11-17
- **Verified Duration:** ~3h 40m (82m status lag)
- **Failure Pattern:** Federated Rail Asymmetry
- **Affected Capabilities:** Payments, Authentication, Mobile Releases
- **Client-Side Operational Gap:** Apple Pay and Sign in with Apple degraded alongside operational card and Google rails while official status acknowledgement lagged by 82 to 88 minutes.
- **Primary Vendor Disclosure:** [Stripe & Claude Status Disclosures](https://status.stripe.com/)
- **Canonical URL:** https://theruntimehq.com/insights/19-apple-november-2026-outage-federated-auth-payment-rails
- **Markdown URL:** https://theruntimehq.com/insights/19-apple-november-2026-outage-federated-auth-payment-rails.md

### Microsoft 365 Outage: Isolating Connector Cascades
- **Provider:** Microsoft 365
- **Incident Date (UTC):** 2026-11-12
- **Verified Duration:** ~24h core (~44h envelope)
- **Failure Pattern:** Ecosystem Connector Cascade
- **Affected Capabilities:** Email & Connectors, AI Integrations, Public Portals
- **Client-Side Operational Gap:** Tenant-bound Exchange and Graph dependencies prevented transparent multi-cloud failover, prolonging impairment inside downstream AI connectors and public portals.
- **Primary Vendor Disclosure:** [Microsoft Service Health (EX1550543 / MO1550821)](https://status.cloud.microsoft/)
- **Canonical URL:** https://theruntimehq.com/insights/18-microsoft-365-november-2026-outage-connector-cascades
- **Markdown URL:** https://theruntimehq.com/insights/18-microsoft-365-november-2026-outage-connector-cascades.md

### Google Cloud's London Outage: Why Zone Redundancy Doesn't Eliminate the Operational Gap
- **Provider:** Google Cloud
- **Incident Date (UTC):** 2026-10-20
- **Verified Duration:** 6h 10m core (8h 10m total)
- **Failure Pattern:** Cross-Zone Failure Cascade
- **Affected Capabilities:** Regional Compute, Managed Databases, Client APIs
- **Client-Side Operational Gap:** A single-zone power loss in europe-west2-b spilled into surviving London zones via failover compute surges and synchronous cross-zone control-plane timeouts.
- **Primary Vendor Disclosure:** [Google Cloud Incident Report](https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj)
- **Canonical URL:** https://theruntimehq.com/insights/15-google-cloud-london-outage-cross-zone-cascades
- **Markdown URL:** https://theruntimehq.com/insights/15-google-cloud-london-outage-cross-zone-cascades.md

### Azure's September 2026 Gateway Incident: The Case for Out-of-Band Operational State
- **Provider:** Microsoft Azure
- **Incident Date (UTC):** 2026-09-30
- **Verified Duration:** 5h 45m
- **Failure Pattern:** Ingress & Management Plane Coupling
- **Affected Capabilities:** Cloud Ingress, Network Gateways, Control Plane APIs
- **Client-Side Operational Gap:** Multi-region gateway connectivity and management plane degradation constrained remote configuration pushes and emergency deployment pipelines.
- **Primary Vendor Disclosure:** [Azure Status History](https://azure.status.microsoft/en-us/status/history/)
- **Canonical URL:** https://theruntimehq.com/insights/12-azure-outage-postmortem-ingress-gateway-failure
- **Markdown URL:** https://theruntimehq.com/insights/12-azure-outage-postmortem-ingress-gateway-failure.md

### Salesforce Outage Postmortem: The In-Band Dependency Trap
- **Provider:** Salesforce
- **Incident Date (UTC):** 2026-09-16
- **Verified Duration:** 7h 36m
- **Failure Pattern:** In-Band Dependency Coupling
- **Affected Capabilities:** CRM & Support, Authentication, Enterprise Portals
- **Client-Side Operational Gap:** Help portal and support intake shared the degraded Hyperforce login tier, stalling customer case creation across 7 hours and 36 minutes of mitigation.
- **Primary Vendor Disclosure:** [Salesforce Incident 20004433](https://status.salesforce.com/incidents/20004433)
- **Canonical URL:** https://theruntimehq.com/insights/10-salesforce-outage-postmortem-the-in-band-dependency-trap
- **Markdown URL:** https://theruntimehq.com/insights/10-salesforce-outage-postmortem-the-in-band-dependency-trap.md

---

## Verification & Sourcing Methodology

- **01. Primary Vendor Disclosures First:** Every postmortem anchors its timeline to official provider status pages, Post-Incident Reviews (PIRs), and primary downstream incident reports. Secondary media coverage is used strictly for corroboration.
- **02. UTC Normalization & Four-Point Timelines:** All timestamps are normalized to UTC and distinguish initial disruption, official vendor acknowledgement, primary customer recovery, and final closure so acknowledgement lag and recovery tails stay visible.
- **03. Explicit Separation of Facts & Architecture:** Provider-reported root causes are separated from architectural interpretation. Our focus is the downstream client operational gap, never criticizing the upstream engineering teams managing complex failures.

---

## Frequently Asked Questions

### How does a RuntimeHQ outage postmortem differ from a vendor Post-Incident Review (PIR)?

A vendor PIR explains the upstream infrastructure or software root cause inside the provider's own systems. Our architectural retrospectives examine the downstream boundary: what happens inside customer-facing web apps, mobile clients, and backend integrations while an upstream dependency is degraded, and which graceful degradation patterns isolate the blast radius.

### Why does multi-zone or multi-region cloud redundancy not eliminate the operational gap?

Infrastructure redundancy protects compute and storage availability, but cross-zone failover surges, synchronous control-plane timeouts, and tenant-bound data gravity still surface errors to client applications. Even when backend infrastructure recovers automatically, clients need out-of-band, machine-readable operational state to guide user journeys during the impaired window.

### When should an application use capability-scoped degradation instead of a global outage banner?

A global banner fits whole-application outages or scheduled maintenance affecting all users. When an upstream outage impacts a single capability, such as Apple Pay checkout authorization or an Exchange email connector, capability-scoped operational state allows the application to degrade only that workflow while keeping parallel or unaffected journeys running normally.

### Why can relying solely on an upstream vendor's status page delay client response?

Public status pages are authored for broad external transparency and often exhibit acknowledgement lag while providers verify scope across tenants. In the November 2026 Apple Services incident, downstream Stripe and Anthropic status logs recorded elevated errors 82 to 88 minutes before Apple's first System Status posting. Decoupled operational state lets your own team declare capability conditions based on your live telemetry.

### Does an Operational State Control Plane prevent upstream cloud or SaaS outages?

No. An Operational State Control Plane does not prevent upstream provider failures, fix internal code bugs, or replace standard error handling and circuit breakers. It provides an out-of-band declaration and edge distribution layer so web, mobile, and backend surfaces coordinate predictable degraded behavior while upstream recovery is underway.