From the Google edition of November 7, 2026
UK Ministry of Justice letter: Oct. 20 Google Cloud incident took courts' Cloud Video Platform down ~4 hours; at least 111 hearings disrupted; continuity plans used Teams, phone and in-person hearings
UK Ministry of Justice / HM Courts & Tribunals Service (letter from the Minister for Courts and Legal Services to the Justice Select Committee) · Courts and tribunals (justice system operations) · England and Wales (international; transferability limited)
- Publisher
- UK Parliament Committees
- Original publication
- 2026-11-02 (letter date; published by the House of Commons Justice Committee)
- Source retrieved
- 2026-11-08
- Event date
- 2026-10-20
What happened
Source finding: the Minister states the Oct. 20, 2026 Cloud Video Platform (CVP) disruption was caused by a wider Google Cloud incident affecting multiple organisations across Europe. A major incident was declared at 08:43; many locations resumed from about 12:30 via a supplier failover, giving roughly four hours of significant disruption. Based on regional returns (not a validated national total), at least 111 hearings were disrupted, delayed, affected or adjourned, notably those relying on prison video links, remote witnesses, interpreters and remote observation. Business continuity used Microsoft Teams, telephone and in-person hearings; HMCTS is reviewing lessons learned. Interpretation: a court service was exposed to a cloud incident indirectly through its video-platform supplier, and local continuity plans limited the impact.
Why it matters
U.S. state courts, corrections video visitation and remote-hearing programs increasingly run on SaaS platforms hosted on hyperscale clouds including Google Cloud. This is a rare government accounting of what one cloud incident did to court operations. Why now: Google published its root cause on Nov. 4 (see The Register item), pairing cause with consequence. Cross-tagged to public-safety because the operational impact is on courts and prison video links.
Evidence and measured results
Official ministerial letter (MoJ ref ADR 139534) answering committee questions. Figures are operational assessments from regional and jurisdictional returns; HMCTS states it holds no real-time national hearing data and ran no formal national data collection during the incident.
Limitations and uncertainty
International (England and Wales); figures are a minimum from partial regional returns; the letter does not describe the CVP supplier's architecture or Google's root cause; impact assessment is the government's own and characterizes impact as limited.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Court and corrections operations depend on cloud-hosted video platforms whose hosting dependencies and failover design are often opaque.
- Stakeholders
- State court administrators
- Court CIOs
- Corrections video-visitation managers
- Public defender and prosecutor IT leads
- Discovery questions
- Which cloud regions/zones host your remote-hearing platform?
- What is the contracted recovery time for a cloud-zone outage?
- Do you have an exercised alternate video path?
- How would prison video links and interpreters be handled during an outage?
- Value hypothesis
- Interpretation: a resilience review could shorten disruption during a future cloud incident; the letter shows continuity plans limited impact, not a quantified saving.
- Potential engagement
- Bounded: dependency mapping and continuity tabletop for one court system's remote-hearing stack.
- Unsupported claims
- That Google Cloud is less reliable than alternatives
- Specific U.S. impact estimates
- That supplier failover will always restore within four hours
Pre-sales engineering
Role takeaway
- Fit
- Relevant to any SLED workload on Google Cloud or on SaaS hosted there, especially real-time video.
- Architecture and integration
- Map SaaS-to-cloud zone dependencies; require multi-zone/region deployment and automated failover; maintain an independent alternate conferencing path.
- Prerequisites
- Supplier disclosure of hosting topology
- Defined RTO/RPO for hearing platforms
- Inventory of hearing types dependent on video
- Constraints
- Agencies rarely control supplier architecture
- International case; U.S. court systems differ
- Data residency may limit region choices
- Security
- Availability risk; alternate platforms must still meet recording, access-control and open-justice requirements.
- Proof of value
- Supplier-run zone failover test with measured restoration time
- Tabletop exercise using the Oct. 20 timeline
- Verify alternate platform can carry prison video links
Delivery
Role takeaway
- Work
- Establish and exercise continuity plans for remote-hearing and video-link services.
- Dependencies
- Platform supplier cooperation
- Court operations and judiciary
- Corrections facilities for video links
- Ownership
- Court operations/administrator's office with IT and supplier management.
- Skills and adoption
- Clerks and judges need practiced procedures for switching to alternate platforms, phone or in-person hearings.
- Governance checkpoints
- Contract review for incident notification and RTO
- Annual continuity exercise
- Post-incident lessons-learned review
- Acceptance criteria
- Proposed: documented alternate path for each hearing type
- Proposed: supplier failover tested at least annually with measured restoration time
- Proposed: incident notification to court operations within a contractually defined window
- Risks
- Untested continuity plans
- Opaque supplier dependencies
- Media/public access gaps during outages
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Courts' video platforms need supplier-level multi-zone or multi-region failover and a tested alternate platform; the letter shows supplier failover restored service in hours, while an alternate collaboration tool and phone hearings bridged the gap.
Governance
Who approves, reviews and stays accountable for outcomes?
Supports requiring cloud and SaaS suppliers to disclose hosting dependencies and failover design, and to report incident timelines to court administrators; HMCTS's own lessons-learned review is pending.
Security and privacy
What data, permissions and controls need testing?
Availability, not confidentiality, was affected; remote observation and media access were impaired, which bears on open-justice obligations.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Interpreters, remote witnesses and remote observers were among the most affected, so continuity plans must cover accessibility and language services.
Procurement
What should contracts, pricing and exit terms secure?
Court technology contracts should require hosting-topology disclosure, zone/region redundancy and incident-notification terms.
Operating model
Which teams own the service once it runs?
Business continuity is a shared court-operations and supplier responsibility that needs regular exercise.
Publication history
- 2026-11-07Google · Issue 106 resources
Stable resource ID: uk-moj-hmcts-cvp-google-cloud-outage-111-hearings-disrupted-20261102