LONDON, United Kingdom – A disruption affecting multiple Google Cloud services in its London region on October 20 caused reported problems for digital banking and other online services, including a service outage at Revolut that affected card payments and ATM withdrawals.
Google identified the affected region as europe-west2 and reported elevated errors and intermittent network failures. Its engineering team was investigating the incident, but the available status information did not establish a root cause or confirm full restoration.
Reuters reported that a person familiar with the matter linked Revolut’s disruption to the Google Cloud incident. ING Germany separately reported technical problems with online and mobile banking logins, but the available reporting did not establish a connection between the two incidents.
The disruption did not establish that every affected website or application shared the same cause, nor that all Google consumer services were unavailable.
What Google confirmed
Google Cloud’s official Service Health dashboard listed an active incident affecting multiple services in europe-west2, its London region.
The incident began at 11:08 p.m. Pacific time on October 19, equivalent to 7:08 a.m. British Summer Time on October 20. Google reported elevated errors and intermittent network failures affecting multiple cloud products.
The company’s incident history listed products spanning computing, storage, databases, networking and other managed services. These included Compute Engine, Google Kubernetes Engine, Cloud Run, Cloud Storage, Cloud SQL and BigQuery, among other products.
Google said its engineering team was investigating and apologized to affected customers. It advised customers to consider moving workloads to another available zone or region where possible.
The published incident information did not identify the underlying technical cause or provide a confirmed restoration time. Google’s dashboard also distinguished the incident from services it did not identify as affected; the incident should not be described as a general outage of all Google products.
The official status page must be checked again immediately before publication because the incident status and affected-product list may change.
Revolut reports payment and withdrawal problems
Revolut reported a disruption affecting multiple services. Its status information showed that card payments and ATM withdrawals were unavailable or partially unavailable during the incident.
Reuters cited a person familiar with the matter who said Revolut’s disruption was related to the Google Cloud incident. This provides a reported connection between the two events, but it does not establish that every Revolut service problem had the same technical cause.
Revolut said its customers’ money and data remained safe. That was the company’s assurance, not an independently conducted audit or proof that every attempted transaction had succeeded or been reversed.
The reported disruption had practical consequences for customers relying on Revolut for payments, cash withdrawals and account access. However, the available reporting did not establish a verified count of affected customers, the total number of failed transactions or whether alternative payment methods were consistently available.
Customers should check their transaction records and follow official company guidance before repeating a payment that appears to have failed. A displayed error does not, by itself, establish whether a transaction was completed, declined or remains pending.
ING Germany’s login problems remain separate
ING Germany separately reported technical difficulties affecting access to online banking and its mobile application.
The reporting available for this article did not establish that Google Cloud caused those problems. The two incidents occurred during the same period, but simultaneous disruptions do not prove a common cause.
Banks and digital businesses may rely on different infrastructure providers, cloud products and internal systems. Establishing a causal link requires supporting evidence, such as a company statement, technical information or reliable reporting that identifies the relevant dependency.
ING Germany’s problems should therefore remain a separate incident unless further evidence establishes a connection.
Other reported website and service problems
Sky News’ live coverage reported difficulties involving other websites and services, including NHS England, NatWest, GOV.UK, Asda, Rightmove and Royal Mail. Other news outlets also reported complaints about banking, delivery and online services.
These reports indicate that users were experiencing problems across a range of services. They do not establish that every named organization confirmed an outage, that all problems occurred at precisely the same time or that Google Cloud caused each disruption.
The available evidence supports three distinct groups:
- Google-confirmed infrastructure incident: Multiple cloud services in the London
europe-west2region were experiencing elevated errors and intermittent network failures. - Business disruption linked by reporting: Reuters cited a person familiar with the matter linking Revolut’s service problems to Google Cloud.
- Separate or unconfirmed disruptions: ING Germany reported login problems without an established causal link, while reports about other websites require individual verification.
A surge in user complaints can help identify a potential outage, but it is not proof of the technical cause. Additional businesses should not be described as confirmed victims of the Google Cloud incident without stronger evidence.
How cloud dependencies create knock-on effects
Cloud providers supply computing capacity, storage, databases, networking and other technical services that businesses use to operate their applications. Customers generally interact with a company’s website or app without knowing which infrastructure supports it.
An application may depend on several cloud services working together. If a required component experiences errors or loses reliable connectivity, the application may fail to load, retrieve information or complete a transaction.
This helps explain how a regional infrastructure incident can coincide with problems across apparently unrelated businesses. Several companies may depend on services in the same cloud region, but they do not necessarily use the same products or have identical technical architectures.
The effect on each business depends on its dependencies, how its systems are deployed and whether workloads can continue through another zone or region. A business with suitable alternative infrastructure may be able to maintain some services, while another may experience more extensive disruption.
The incident does not, by itself, establish that any named business lacked adequate safeguards. Assessing resilience requires evidence about its architecture, redundancy, disaster-recovery arrangements and response to the incident.
Customer impact and recovery questions
For customers, the immediate concern was whether they could access accounts, make payments or withdraw cash. Revolut reported problems with card payments and ATM withdrawals, while ING Germany reported login difficulties.
The available reporting did not establish whether all customers were affected equally, how many transactions failed or whether alternative banking channels were available in every affected location. These details should not be assumed.
Recovery also involves more than the restoration of a cloud service. Individual businesses may need to confirm that applications are working, connections have recovered and pending transactions have been handled correctly. Any lingering effects require confirmation from the relevant company.
Google’s suggestion that customers consider moving workloads to another available zone or region was guidance for customers able to do so. It did not confirm that every customer could migrate immediately or that relocation would resolve every downstream problem.
Resilience and dependence on cloud infrastructure
The incident highlights the operational questions businesses face when they depend on large cloud providers for services used by customers every day.
Important questions include whether critical workloads can operate in another region, whether backup systems remain independent of the affected infrastructure, and whether recovery arrangements have been tested under realistic conditions.
A regional outage can expose dependencies that may not be apparent during normal operations. But the existence of an outage is not evidence that a particular business failed to plan adequately. That conclusion would require company-specific information about its systems and continuity measures.
Clear communication is also important. Cloud providers need to explain which services and locations are affected, while downstream businesses need to tell customers which functions are unavailable and how to check transaction or account status.
Latest status and remaining uncertainty
At the latest Google Cloud status check retrieved for this draft on October 20, the London-region incident was listed as active. Google had not disclosed a root cause or confirmed full restoration in the incident information available at that check.
Reuters linked Revolut’s reported disruption to Google Cloud through a source familiar with the matter. ING Germany’s login problems and the other reported website difficulties remained unconnected to Google Cloud on the evidence available for this article.
The final publication check must establish whether Google has updated the incident status, whether Revolut and ING Germany have restored their services, and whether any additional companies have confirmed a disruption or its cause.
Attribution note: The reported link between Google Cloud and Revolut is attributed to a person familiar with the matter cited by Reuters. ING Germany’s login difficulties and other reported service problems are not attributed to Google Cloud without further supporting evidence.
