A power-related failure at Google Cloud’s London infrastructure disrupted banking services, online platforms and public-sector systems across the UK on Tuesday, 20 October, exposing the risks of growing dependence on a small number of technology providers.
The disruption affected Google Cloud’s europe-west2 region, which serves London, and caused elevated error rates and intermittent network failures across multiple services. Google’s official service-status dashboard subsequently marked the incident as resolved, recording a total duration of 7 hours and 52 minutes. The company said its engineering teams were investigating the issue and apologised to affected customers.
The incident demonstrated how a technical failure deep within the digital infrastructure can quickly become a problem for everyday services, from checking bank balances to accessing online public services.
Banks and public services among those affected
Several major financial institutions experienced disruption during the incident, including Lloyds, Halifax, HSBC and Revolut, according to reporting by the Associated Press. Rightmove and other online services were also reported to have experienced problems. Some court hearings were affected because of disruption to the Cloud Video Platform used for remote proceedings.Google attributed the incident to a power-related event in its London region. In an update reported by The Independent, the company said: “The power event is mitigated.” Google also indicated that it would publish a fuller analysis after completing its internal investigation. Although services began recovering, the disruption raised concerns about the potential consequences when businesses and public institutions depend on infrastructure operated by a third party.
For customers, even a temporary outage can mean difficulty accessing accounts, completing payments or using digital services. For organisations, it can interrupt operations, delay transactions and create additional pressure on customer-support teams.
UK Parliament seeks answers from financial regulators
The incident has prompted scrutiny from Westminster. On 20 October, the House of Commons Treasury Committee announced that its chair, Dame Meg Hillier, had written to the Governor of the Bank of England and the chief executive of the Financial Conduct Authority (FCA) seeking answers about the disruption and the oversight of critical technology providers. The committee highlighted the government’s existing Critical Third Parties regime, designed to strengthen oversight of external suppliers whose services are important to the UK financial system.
According to the committee, four companies were designated under the regime in July 2026: Microsoft Ireland Operations Limited, Google Cloud EMEA Limited, Amazon Web Services EMEA SARL and Oracle Corporation UK Limited. The committee’s action is significant because it places the outage within a wider debate about whether financial regulators have sufficient oversight of technology companies that support essential services.
The committee’s announcement did not establish that the outage threatened the stability of the UK financial system. Instead, it raised questions about how the existing regulatory powers should be used in response to incidents of this kind.
A wider test of Britain’s digital resilience
The incident also affected online payment services beyond banking. South Oxfordshire District Council, for example, warned residents that some users might experience difficulties with its payment pages because of a failure at a Google data centre. The council said Google had indicated that service would resume shortly.
The notice illustrated how a problem affecting a cloud infrastructure provider can reach local government services, even when the council itself is not operating the failed infrastructure.
Cloud computing allows organisations to store data, run applications and deliver online services without maintaining all the necessary infrastructure themselves. However, when multiple organisations depend on the same provider or regional infrastructure, one incident can affect numerous services at once.
The challenge is not limited to preventing individual failures. Organisations must also ensure that essential operations can continue when a supplier becomes unavailable. Possible safeguards include tested backup systems, alternative infrastructure, effective incident communication and recovery plans. The Google incident does not, by itself, establish that every affected organisation lacked adequate backup arrangements. Determining why individual services failed and how quickly they recovered will require further investigation.
What happens next?
Google’s official incident record confirms that the disruption has been closed, but the company’s promised incident analysis will be important in establishing the precise cause, the technical systems affected and the measures planned to prevent a recurrence.
The Treasury Committee’s questions to the Bank of England and the FCA may also help clarify how regulators assess the resilience of critical cloud providers and what lessons should be drawn from the incident. For Britain, the central issue is increasingly clear: digital resilience depends not only on the reliability of individual companies but also on how effectively the organisations using their services prepare for disruption.
As banks, local authorities and other institutions move more operations online, the ability to keep essential services running during a technology failure will become a test of public trust as well as technical capability.
