Draft, not yet released. In stewardship review. Not indexed until the first approved release.

Shared control-plane fault with diverging sovereignty rules

A conditional statement under stated assumptions, never a prediction.

2 min read0 figures0 tables3 notesNR-XTECH-CLOUD-GLOBAL-2026-BASELINE

Contents
  1. ·Edition home
  2. ·Executive summary
  3. 1Cloud is shared infrastructure with a physical footprint
  4. 2Key findings
  5. 3Systems and sectors at baseline
  6. 4Risks and capability
  7. 5Shared control-plane fault with diverging sovereignty rules
    1. 5.1 Assumptions
    2. 5.2 The cascade, step by step
    3. 5.3 The scenario as a table of steps
  8. 6Readings from the other desks
  9. 7The 2027 agenda
  10. 8Systems in depth
  11. AMethodology
  12. BData appendix
  13. CReferences and record
  14. ·Complete edition, for print

5.1Assumptions

Scenario SCN-XT08-DEP-01: what is assumed, and what is held constant.

Baseline
the 2026 reference state in this edition
Drivers
a fault in a shared provider control plane lasts many hours while public services depend on it and sovereignty rules limit failover
Analogues
the 2025 events at AWS, Google Cloud and Cloudflare202122
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. 1

    INF → DAT

    a control-plane fault interrupts dependent services in one region

    2025

  2. 2

    DAT → FIN

    payment and business services stall until recovery

    2025

  3. 3

    DAT → HLT

    hosted records and booking services become unavailable

    2025

  4. 4

    GOV → INF

    sovereignty rules limit moves between providers or regions

    2026

  5. 5

    ENE → INF

    recovery load meets local grid limits at the host region

    2024

  6. 6

    FIN → INF

    customers re-weigh dependence as switching charges end

    2025

5.3The scenario as a table of steps

How the shock in scenario SCN-XT08-DEP-01 would travel through Cloud, Edge and Distributed Computing’s coupled systems, step by step, under the assumptions the edition states.

StepWhat happensSource
01 Infrastructure to datA control-plane fault interrupts dependent services in one region. Analogue or source: 2025.Edition XT-08, scenario SCN-XT08-DEP-01, step 1
02 DAT to financePayment and business services stall until recovery. Analogue or source: 2025.Edition XT-08, scenario SCN-XT08-DEP-01, step 2
03 DAT to healthHosted records and booking services become unavailable. Analogue or source: 2025.Edition XT-08, scenario SCN-XT08-DEP-01, step 3
04 Governance to infrastructureSovereignty rules limit moves between providers or regions. Analogue or source: 2026.Edition XT-08, scenario SCN-XT08-DEP-01, step 4
05 Energy to infrastructureRecovery load meets local grid limits at the host region. Analogue or source: 2024.Edition XT-08, scenario SCN-XT08-DEP-01, step 5
06 Finance to infrastructureCustomers re-weigh dependence as switching charges end. Analogue or source: 2025.Edition XT-08, scenario SCN-XT08-DEP-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: Cloud, Edge and Distributed Computing 2026, scenario SCN-XT08-DEP-01 (2026); Cloud, Edge and Distributed Computing 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

  1. 20Amazon Web Services (ed.), Summary of the Amazon DynamoDB Service Disruption in the Northern Virginia (US-EAST-1) Region (post-event summary; 19 October 11:48 PM to 20 October 2:20 PM PDT; latent race condition in the DNS management system for the regional endpoint; services and times listed; operator report). Amazon Web Services, Seattle. Observation year 2025. Accessed 2026-11-03.back
  2. 21Google Cloud (ed.), Incident report for the Service Control outage of 12 June 2025 (status page; 10:51 to 18:18 PDT by the incident header; mini report gives different times; policy data with blank fields caused a null pointer crash in Service Control; operator report). Google, Mountain View. Observation year 2025. Accessed 2026-11-03.back
  3. 22Cloudflare (ed.), Cloudflare outage on November 18, 2025 (blog post; start 11:20 UTC; core traffic largely restored 14:30 UTC; full recovery 17:06 UTC; Bot Management feature file doubled in size and exceeded a limit of 200 features; not caused by a cyber attack, per the operator). Cloudflare, San Francisco. Observation year 2025. Accessed 2026-11-03.back

Cite this chapter

Valadbaygi, S. (Ed.). (2026). Chapter 5: Shared control-plane fault with diverging sovereignty rules. In Exponential Technology Report 2026: Cloud, Edge and Distributed Computing (Baseline Edition 2026, Report No. NR-XTECH-CLOUD-GLOBAL-2026-BASELINE) [Draft under review]. The Global Centre for Risk and Innovation (GCRI).

Every citation form of the whole report, BibTeX and RIS included, is on the edition home. Cite this report

ReportsContribute

Send evidence or a correction on Cloud, Edge and Distributed Computing.

Reports is the Consortium’s quarterly publication, written by six desks. This page sits with the Global Centre for Risk and Innovation (GCRI) Systems Evidence desk. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work. Sent to the wrong desk, it is forwarded, not refused.

GCRI Systems Evidence deskExponential Technology

Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.

CC BY 4.0 Free to read. Text and figures: CC BY 4.0. Data: CC0 1.0. Authors keep copyright. Published by GCRI Canada.

The Global Centre for Risk and Innovation

Science · evidence · measurement

Not for profit

Our articles, maps and twins are free to read and free to republish. Readers and partners keep it that way.

Partner with us

Who funds us

GCRI is a not-for-profit institution. To ask who funds a piece of work, use the funding questions form.

Independence

Editors and the expert reviewers named on each article decide what we publish. Funders and partners do not review or approve articles before publication.

Corrections policy

Licence

Articles: CC BY 4.0. Figures, maps, twins and data: CC BY 4.0. Other uses: ask through the permissions form.

Privacy choices