Your card gets declined at the coffee counter. The banking app will not let you sign in. The transfer you sent an hour ago is stuck. On Tuesday morning, October 20, 2026, that was the experience for customers of some of the biggest names in banking — not because their banks were hacked, but because one part of Google's cloud broke. A failure in Google Cloud's London region, known as europe-west2, disrupted dozens of Google services and knocked banking and everyday apps sideways, with Revolut's services reported offline worldwide and Lloyds, HSBC, Halifax, Royal Mail, DPD and Rightmove all logging problems.
Google confirmed the incident on its service health page, saying it was "experiencing an issue with multiple services in europe-west2," with cloud services seeing errors and intermittent network failures. Reports of the failure began around 07:00 London time on Tuesday — late Monday night in the United States. By mid-morning in the UK, more than 1,500 people had reported problems with Revolut alone on the outage tracker Downdetector, and Google still had not named a cause or given a recovery time.
Key Takeaways
- Google Cloud's europe-west2 (London) region suffered a multi-service outage on Tuesday, October 20, 2026, with errors and intermittent network failures across dozens of services including Compute Engine, BigQuery, Cloud Storage, Cloud Run and Kubernetes Engine.
- Revolut was hit hardest in public view: card payments, transfers, ATM withdrawals, sign-ins, top-ups, stock trades and crypto were all flagged as disrupted, and Bloomberg and The Register reported its services offline worldwide. Revolut says customers' money and data are safe.
- Lloyds, Halifax and HSBC customers also reported problems, along with Royal Mail, DPD, Rightmove and the budgeting app Emma. Lloyds said its app was not fully down but that some customers were having problems with some online services.
- Nothing so far points to a hack. Google called it a technical incident under investigation, Emma told customers "this is a technical outage, not a security issue," and Google advised business customers who could to move workloads to another region.
What Happened in Google's London Region
Modern banking apps do not live inside the bank. They run on rented cloud infrastructure, and a large share of it sits in a small number of data-center regions. Europe-west2 is Google Cloud's London region, and on Tuesday morning it became the single point of failure for a long list of services at once.
Google's own incident listing named dozens of affected products — among them AlloyDB, Apigee, Cloud Firestore, Cloud Load Balancing, Cloud NAT, Cloud Run, Cloud Spanner, Cloud SQL, Cloud Storage, Compute Engine, Google BigQuery, Kubernetes Engine, Pub/Sub and Virtual Private Cloud. In plain English: the computing, storage, networking and database plumbing that other companies build their apps on top of. When that plumbing fails in one region, every app that depends on that region feels it at the same time — which is why a bank, a postal service, a parcel company and a property website can all break on the same morning from one incident.
Google's guidance to its business customers was telling: if it is feasible, try migrating the affected workload to another available zone or region. That is sound engineering advice, but it is also an admission that, at that point, the fastest fix for customers was to leave the region rather than wait for it. The Register reported that Google gave no recovery time, and Google's public updates through the morning stuck to the same lines — engineers investigating, and an apology "to all who are affected by the disruption."
What Revolut, Lloyds and HSBC Customers Actually Saw
Revolut took the most visible damage. The fintech flagged problems across nearly everything it does: card payments, money transfers, ATM withdrawals, signing into accounts, top-ups, stock trades and cryptocurrency. Customers posted on X about cards being declined, including one user who said a declined card left them struggling to get home from a late shift. Revolut's own statement on X said it was "currently experiencing a service disruption affecting multiple services," and a spokesperson added the line every customer needed to hear: "We can confirm that all our customers' money and data are safe. We've been working to fix the issue since it was identified this morning."
The traditional banks were hit unevenly. Hundreds of Lloyds Bank and HSBC users reported issues to Downdetector. A Lloyds spokesperson pushed back on the word "down," saying: "Our app isn't down, but we're continuing to monitor the situation closely. We're aware some customers may be having problems with some online services this morning, alongside similar issues affecting a number of organisations." Halifax, which Lloyds Banking Group owns, told a customer on X it was aware some customers were having issues with its app and online services and was "working hard to fix it." Bank of Scotland customers reported problems too.
Beyond banking, the outage tracker lit up for Royal Mail, parcel firm DPD and property site Rightmove, and the budgeting app Emma simply told customers it was offline: "Emma is currently down due to a Google Cloud outage affecting services in London since 7am." One honest caution applies to the longer tail of names: during a big cloud incident, Downdetector spikes appear for services that may have separate, unrelated problems, and it has not been confirmed that every reported disruption on Tuesday morning traces back to Google Cloud. The confirmed core is Google's own service list, Revolut, Lloyds/Halifax's statements, and the apps like Emma that named Google Cloud directly.
Why a London Outage Reached Customers Worldwide
The detail that should get the attention of American readers is the word "worldwide." Bloomberg and The Register both reported Revolut's services offline worldwide, not just in Britain — a London region can hold live data and services for customers on other continents, and Revolut operates in the United States as well as Europe. A US Revolut customer trying to pay or transfer on Tuesday morning was, in effect, waiting on a data center an ocean away.
That is not a Revolut-only lesson. American banking and fintech apps also concentrate on a handful of cloud regions run by Google, Amazon and Microsoft, and US outages at those providers have repeatedly shown the same pattern: one regional failure, dozens of unrelated apps down together. It is the flip side of the cloud's convenience — the same Google that just put one shared cart across Search and Gemini, as we reported in our coverage of the Google Universal Cart launch in the US, also concentrates the plumbing underneath other companies' apps.
There is a personal version of the same lesson. When your only copy of a bank statement, an ID scan or a payment receipt lives inside one app, an outage locks you out of your own records at exactly the moment you need proof of a payment. Keeping private financial documents, ID scans and important receipts in local, on-device storage such as Pro Calculator Secure Vault — which stores files on the phone itself and collects no data — means a cloud failure somewhere else never becomes your paperwork emergency.
Scam Warning: Outages Are Phishing Season
Every major banking outage is followed within hours by fake "service restored — verify your account" texts and emails, and by bogus support accounts replying to frustrated customers on social media. Revolut, Lloyds and HSBC will never text you a link to "unlock" an account after an outage, never ask for your full PIN or a one-time code, and never ask you to move money to a "safe account." If a payment failed during the outage, check its status inside the official app only. If a message about the outage arrives from anyone else, treat it as a scam until the bank's own status page says otherwise.
Outage Checklist: What to Do When Your Banking App Goes Down
- Check whether it is just you. Look at Downdetector and the bank's official status page or verified social account before assuming your account has a problem.
- Do not keep retrying a failed payment. A transfer that looks stuck during an outage may still complete once systems recover; sending it twice can mean paying twice.
- Keep evidence. Screenshot error messages and declined-payment notices with the time visible — banks advise customers who miss a payment because of an outage to gather proof of any charges or harm.
- Use a backup way to pay. A second card or a small cash buffer covers the coffee-and-train-home situations that outage mornings create.
- Wait for the all-clear inside the app. Once service is restored, re-check balances and pending transfers in the official app — not through any link sent to you.
Frequently Asked Questions
What caused the Google Cloud outage on October 20?
Google had not announced a root cause at the time of writing. Its status page described an issue affecting multiple services in the europe-west2 (London) region, producing errors and intermittent network failures, and said its engineering team was investigating. Google apologized for the disruption and suggested business customers move workloads to another region where feasible.
Was Revolut or any bank hacked?
There is no evidence of a hack in this incident. Revolut stated that all customers' money and data are safe, the budgeting app Emma told customers "this is a technical outage, not a security issue," and Google framed the event as a cloud service failure. The danger after an outage is not the outage itself but the phishing messages that imitate banks while customers are distracted.
Which services were affected by the Google Cloud outage?
Google listed dozens of its cloud products, including Compute Engine, Kubernetes Engine, BigQuery, Cloud Storage, Cloud SQL, Cloud Run, Firestore and Load Balancing. On the consumer side, Revolut reported the widest disruption; Lloyds, Halifax and HSBC customers reported problems, and Royal Mail, DPD, Rightmove and Emma were among the other services flagged. Not every Downdetector spike that morning has been confirmed as part of this incident.
I am in the US. Could a foreign cloud outage affect my banking app?
Yes. Bloomberg and The Register reported Revolut's services offline worldwide from a London region failure, and Revolut serves US customers. More broadly, US fintech and banking apps rely on the same small set of cloud providers and regions, so a single regional failure — at home or abroad — can take unrelated apps down together.
How can I keep my financial documents reachable during an app outage?
Keep your own local copies. Pro Calculator Secure Vault stores photos, videos, audio, documents and private notes locally on your device, protected by sign-in protection and an intruder selfie feature, alongside an incognito private browser and 8 smart calculators — standard, floating, BMI, age, currency, tip, GST & VAT and loan EMI. No data is collected or shared with third parties, and because the files live on the phone, no cloud outage can lock you out of them.
The Bottom Line
Tuesday's outage was not a bank failure and not a breach — it was a reminder of how much of modern banking sits on a few shared foundations. One Google Cloud region in London stumbled, and within hours a worldwide fintech, three major UK banking brands, the postal service and a property portal were all apologizing on the same morning. Google will eventually publish what went wrong in europe-west2; until then, the practical takeaways for US readers are to verify outages before panicking, never re-send a stuck payment, ignore every "verify your account" message that rides on the news, and keep your own copies of the documents that matter. Pro Calculator Secure Vault is built by ZAS — you can see more of our apps on our developer page on Google Play.
No comments:
Post a Comment