Shared provider failure that overlaps a power or network loss
A conditional statement under stated assumptions, never a prediction.
Contents
- ·Edition home
- ·Executive summary
- 1Digital systems fail together
- 2Key findings
- 3Systems and sectors at baseline
- 4Risks and capability
- 5Shared provider failure that overlaps a power or network loss
- 6Readings from the other desks
- 7The 2027 agenda
- 8Systems in depth
- AMethodology
- BData appendix
- CReferences and record
- ·Complete edition, for print
5.1Assumptions
Scenario SCN-SR10-DPI-01: what is assumed, and what is held constant.
- Baseline
- the 2026 reference state in this edition
- Drivers
- a configuration or DNS fault at a shared cloud or edge provider, coinciding with a regional power or network loss
- Analogues
- cloud event, October 2025; edge event, November 2025; software outage, 2024345
- Interventions
- none modelled: the specification describes the unmitigated case
- Run state
- narrative specification; quantified run scheduled for 2027
5.2The cascade, step by step
- 1
INF → DAT
a shared provider fault removes a regional endpoint or an edge network
2025
- 2
DAT → FIN
payment and identity checks fail or time out at dependent services
2025
- 3
ENE → INF
a regional power loss cuts exchanges and data centres to batteries and generators
2026
- 4
DAT → HLT
records, claims and dispatch services degrade
2024
- 5
DAT → DEV
services with no offline path exclude users with no fallback
2025
- 6
INF → FIN
payments pause; losses accumulate
2024
5.3The scenario as a table of steps
How the shock in scenario SCN-SR10-DPI-01 would travel through Digital Public Infrastructure and Systemic Cyber Risk’s coupled systems, step by step, under the assumptions the edition states.
| Step | What happens | Source |
|---|---|---|
| 01 Infrastructure to dat | A shared provider fault removes a regional endpoint or an edge network. Analogue or source: 2025. | Edition SR-10, scenario SCN-SR10-DPI-01, step 1 |
| 02 DAT to finance | Payment and identity checks fail or time out at dependent services. Analogue or source: 2025. | Edition SR-10, scenario SCN-SR10-DPI-01, step 2 |
| 03 Energy to infrastructure | A regional power loss cuts exchanges and data centres to batteries and generators. Analogue or source: 2026. | Edition SR-10, scenario SCN-SR10-DPI-01, step 3 |
| 04 DAT to health | Records, claims and dispatch services degrade. Analogue or source: 2024. | Edition SR-10, scenario SCN-SR10-DPI-01, step 4 |
| 05 DAT to development | Services with no offline path exclude users with no fallback. Analogue or source: 2025. | Edition SR-10, scenario SCN-SR10-DPI-01, step 5 |
| 06 Infrastructure to finance | Payments pause; losses accumulate. Analogue or source: 2024. | Edition SR-10, scenario SCN-SR10-DPI-01, step 6 |
A teaching model of a conditional scenario under the edition’s stated assumptions: not a forecast, not a prediction and not a warning. Sources: Digital Public Infrastructure and Systemic Cyber Risk 2026, scenario SCN-SR10-DPI-01 (2026); Digital Public Infrastructure and Systemic Cyber Risk 2026, references (NR-CIT-1) (2026).
Notes
Numbers are the edition’s reference numbers, so a note reads the same in every chapter. The full list, with every source and its licence, is in Annex C. Annex C, references
- 3Microsoft (ed.), Helping our customers through the CrowdStrike outage (blog post of 20 July 2024; estimate of 8.5 million Windows devices, less than one percent of all Windows machines). Microsoft, Redmond. Observation year 2024. Accessed 2026-11-03.back
- 4Amazon Web Services (ed.), Summary of the Amazon DynamoDB service disruption in the Northern Virginia (US-EAST-1) Region, 19 to 20 October 2025 (post-event summary). Amazon Web Services, Seattle. Observation year 2025. Accessed 2026-11-03.back
- 5Cloudflare (ed.), Cloudflare outage on November 18, 2025 (incident report). Cloudflare, San Francisco. Observation year 2025. Accessed 2026-11-03.back
