Google Cloud Compute and SQL Failures in London Halt Revolut App and Card Payments for Millions

A widespread infrastructure failure in Google Cloud’s London region disrupted services for multiple organizations, including fintech Revolut. The incident began at 07:08 UK time in the europe-west2 region. Google’s service health dashboard indicated that dozens of core cloud products were experiencing issues. Customers reported higher-than-normal error rates and intermittent network faults. Engineers were investigating the root cause at the time of reporting.

Root cause

Google has not confirmed the specific technical cause of the outage. The company stated that its engineers were actively looking for the source of the disruption. No patch or fix has been confirmed yet. Google apologized for the disruption and advised customers to move workloads to other zones or regions if possible. A next update was scheduled for noon UK time, but no full restoration timeline was provided.

Attack path

This incident is an infrastructure availability failure, not a security breach or attack. Users experienced service unavailability rather than data exfiltration or unauthorized access. Revolut’s systems, which run on Google Cloud, became unreachable due to the underlying platform failure. The outage prevented legitimate transactions and app access. There is no evidence of malicious exploitation or compromise of customer data in this event.

Affected versions

• Compute Engine
• Kubernetes Engine
• Cloud SQL
• Cloud Storage
• BigQuery
• Other Google Cloud products in the europe-west2 region

Mitigation

• Move workloads to alternative availability zones or regions if feasible.
• Monitor Google’s service health page for official updates and status changes.
• Implement redundancy across multiple cloud regions to reduce single-point-of-failure risk.
• Verify that failover procedures are tested and operational for critical services.

Detection notes

Teams usually detect infrastructure outages through sudden spikes in error logs and failed health checks. Monitoring dashboards will show increased latency and connection timeouts from external endpoints. Alerting systems may trigger on unexpected drops in traffic volume or service response rates. Check whether dependent services are failing due to upstream provider issues. Verify that authentication and data storage layers are also impacted. Isolate affected components to prevent cascading failures. Document the timeline of failures for post-incident review.

Background: Data exfiltration

Data exfiltration prevention requires monitoring outbound traffic for anomalies, restricting user permissions through strict access controls, and encrypting sensitive files at rest. You must detect unusual data movement patterns early, block unauthorized transfer methods, and verify that backup systems remain intact to limit exposure during a breach.

Read the full guide: Data Exfiltration Prevention: Stop Hidden Data Theft Before It Escapes

What to do and how to stay safe: Google Cloud

• Check your cloud provider’s status page for confirmed outages in your region.
• Verify if your applications are relying on single-region infrastructure.
• Review your disaster recovery plan for multi-region failover capabilities.
• Monitor application logs for unusual error patterns during service disruptions.

Step-by-step guide: MFA for Cloud Accounts: 8 Practices to Prevent Credential Theft

General security guidance from the BlueTeam Insider newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What caused the Revolut outage?

The Revolut outage was related to a Google Cloud disruption in the London region, according to a person familiar with the matter told Reuters.

Which Google Cloud products were affected?

Google listed 36 affected products, including Compute Engine, Kubernetes Engine, Cloud SQL, Cloud Storage, and BigQuery.

When did the outage start?

Problems began at 07:08 UK time in the europe-west2 London region, according to Google’s service health page.