The 2027 agenda
Eight bounded questions open the 2027 cloud agenda. Each comes from a baseline finding, names the initiative that will carry it and the first output due in the 2027 cloud edition.
Contents
- ·Edition home
- ·Executive summary
- 1Cloud is shared infrastructure with a physical footprint
- 2Key findings
- 3Systems and sectors at baseline
- 4Risks and capability
- 5Shared control-plane fault with diverging sovereignty rules
- 6Readings from the other desks
- 7The 2027 agenda
- 8Systems in depth
- AMethodology
- BData appendix
- CReferences and record
- ·Complete edition, for print
7.1Questions for the operational series
- C-01
Which public and critical services depend on one provider, region or control plane, and what happens when it fails?
INI-XT08-DEP-01 · dependency map; first output: dependency register.
- C-02
What load do new facilities add to local grids, and how long do connections take?
INI-XT08-ENE-02 · grid and load; first output: site and grid table.
- C-03
Can operator water and efficiency figures be put on a common basis?
INI-XT08-WAT-03 · water and efficiency basis; first output: metric comparison.
- C-04
How many organisations have tested an exit or a switch between providers?
INI-XT08-EXT-04 · exit and switching tests; first output: test evidence table.
- C-05
How large is the edge layer in energy, sites and devices?
INI-XT08-EDG-05 · edge footprint; first output: edge inventory note.
- C-06
Which national rules on data location and sovereignty differ, and how?
To be admitted in 2027; first output: rule overlay.
- C-07
What workforce exists for data centres, cloud operations and resilience engineering?
To be admitted in 2027; first output: scoping note.
- C-08
Which readiness capabilities have been tested in real events, and which are only planned?
Readiness capability register; first output: rung evidence for 15 functions.
7.2Portfolio proposed for the Q1 2027 alignment
Five initiatives and one Universe mission candidate are proposed for the 2027 cloud portfolio. They are programme objects: no partner, funder or member is attached to them in this edition.
| ID | Object | Kind | Question | State |
|---|---|---|---|---|
| INI-XT08-DEP-01 | Dependency map | Initiative | C-01 | PROPOSED |
| INI-XT08-ENE-02 | Grid and load | Initiative | C-02 | PROPOSED |
| INI-XT08-WAT-03 | Water and efficiency basis | Initiative | C-03 | PROPOSED |
| INI-XT08-EXT-04 | Exit and switching tests | Initiative | C-04 | PROPOSED |
| INI-XT08-EDG-05 | Edge footprint | Initiative | C-05 | PROPOSED |
| MSN-XT08-2027-01 | Shared control-plane fault Universe mission | Mission | C-01 | Candidate |
7.3The pathway
The cloud edition reads national readiness chapters, the coupled sector reports on energy, cyber and digital systems and infrastructure, and the global edition through one governed evidence graph. At baseline the federation is designed; the global energy and lifeline editions are drafted. This page states what exists today and what comes next.
- 01
National readiness chapters
cloud dependence and data centre load in each national edition
IN PREPARATION · national baselines
- 02
Sector couplings
GS-02 energy · GS-13 cyber and digital systems · SR-10 digital public infrastructure
GS-02 DRAFTED · sector baselines
- 03
Technology system model
facilities, grid, water, market, resilience, governance
v0 SPECIFIED · v1 with federation evidence
- 04
Strategic links
SR-02 lifeline systems · XT-06 semiconductors and compute
PLANNED · strategic baselines
- 05
Universe
annual proving environment
CANDIDATE MISSION · mandate in 2027
- 06
XT-08 report
this series
BASELINE DRAFT · 2027 annual edition
- 07
Evidence and correction
one graph, many projections
OPEN · first correction cycle in 2027
7.4Universe 2027: evidence pack for the cloud candidate mission
- 01
Mandate
- 02
Core Build · 1 month
- 03
Action · 1 week
- 04
Evidence seal
- 05
Portfolio correction
- 06
Next mandate
| Item | Record | State | Timing |
|---|---|---|---|
| F1 | Annual mandate record | PLANNED | after the Q2 2027 alignment |
| F2 | Core Build record | PLANNED | one month before the exercise |
| F3 | Exercise evidence | PLANNED | during the Action week |
| F4 | Decision packets | PLANNED | exercise state only |
| F5 | Proof receipts | PLANNED | scoped to each recorded check |
| F6 | After-action report | PLANNED | within one quarter |
| F7 | Upgrade docket | PLANNED | routed to the Portfolio |
| F8 | Portfolio renewal | PLANNED | 2027 global annual edition |
| F9 | Public synthesis | PLANNED | public-safe extracts only |
Mission
- ID
- MSN-XT08-2027-01 · Shared control-plane fault Universe mission
- Role spine
- Leadership sponsor · Institutional anchor · Mission lead: drawn from national pathways
- Receiving actors
- to be identified with the mandate
7.5Handoffs and routing
Where the baseline’s findings go next. A handoff routes a finding for awareness, review or work; it transfers no authority.
| Finding | Routed to | Purpose | Class |
|---|---|---|---|
| ENE-001 · global electricity | INI-XT08-ENE-02 | grid and load | PUBLIC |
| ENE-003 · Irish grid share | INI-XT08-ENE-02 | grid and load | PUBLIC |
| ENE-005 · PUE baselines | INI-XT08-WAT-03 | water and efficiency basis | PUBLIC |
| WAT-006 · water reports | INI-XT08-WAT-03 · key F review | water and efficiency basis | PUBLIC |
| FIN-008 · market shares | INI-XT08-DEP-01 | dependency map | PUBLIC |
| GOV-010 · switching rules | INI-XT08-EXT-04 | exit and switching tests | PUBLIC |
| INF-011 · outages | INI-XT08-DEP-01 | dependency map | PUBLIC |
| SYS-012 · compound pathway | MSN-XT08-2027-01 | Universe candidate | CONSORTIUM |
| Class | Where it goes | Who can see it |
|---|---|---|
| PUBLIC | the published edition and its evidence bundle | anyone |
| CONSORTIUM | governed rooms of the federation | consortium members under agreement |
| CONTROLLED | need-to-know channels | named competent actors only |
7.6Feeds and signal register
| Feed | Producer | Latency | Feeds into |
|---|---|---|---|
| Operator status and post-event reports | AWS, Google Cloud, Cloudflare and others | per event | INF-011 |
| Global electricity and data centre reports | IEA | periodic | ENE-001 |
| National data centre electricity statistics | statistics offices and laboratories | annual | ENE-003 |
| Operator sustainability reports | Google, Microsoft, Amazon | annual | ENE-004 |
| Cloud market releases | industry analysts | quarterly | FIN-008 |
| EU competition and digital policy pages | European Commission | per release | GOV-009 |
| UK competition case page | UK CMA | per release | GOV-009 |
Escalation routes
- none · keep monitoring
- research question
- project
- risk object
- annual publication
- signal report
| ID | Signal | Corroboration | Systems | Route |
|---|---|---|---|---|
| SIG-XT08-001 | Three providers held 63% of cloud infrastructure revenue in Q2 202610 | CORROBORATED | FIN · INF | research question C-01 |
| SIG-XT08-002 | Competition reviews of cloud opened in the UK and EU1112 | CORROBORATED | GOV · FIN | initiative C-04 |
| SIG-XT08-003 | Three large events in 2025 traced to internal faults202122 | PARTIAL | INF · DAT | research question C-01 |
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
- 10Synergy Research Group (ed.), Q2 Cloud Market Passes $143 Billion; Highest Growth Rate in Eight Years (release of 30 July 2026; Amazon 28%, Microsoft 20%, Google 15%; quarterly revenue USD 143.4 billion; growth 43%; definition IaaS, PaaS and hosted private cloud; industry analyst). Synergy Research Group, Reno. Observation year 2026. Accessed 2026-11-03.back
- 11UK Competition and Markets Authority (ed.), Cloud services market investigation (case page; final decision published 31 July 2025; recommends prioritising strategic market status investigations of Microsoft and AWS; board decision expected in the first quarter of 2026; the decision documents were not opened). Competition and Markets Authority, London. Observation year 2025. Accessed 2026-11-03.back
- 12European Commission (ed.), Commission opens market investigations into cloud computing services under the Digital Markets Act (announcement of 18 November 2025; two investigations on whether AWS and Microsoft Azure should be designated and one on whether the DMA fits cloud). Directorate-General for Communications Networks, Content and Technology, Brussels. Observation year 2025. Accessed 2026-11-03.back
- 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
- 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
- 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
