Your Crypto Was Safe. You Still Couldn't Get to It.

I opened the Revolut app just past 7am my time to shift a little money and got the spinning wheel. Then an error message. Then the wheel again. My first thought wasn't panic about my balance. It was a much less comfortable question: how much of my money is currently sitting behind a single login that I don't control?

What Actually Broke

Here's the granular version, because the headlines flattened it. At 06:08 UTC, Google Cloud's europe-west2 region, its London footprint, ran into technical trouble. Revolut's crypto trading, card payments and bank transfers all went sideways. Early morning in London, which happens to be exactly when people check balances before work and merchants start processing the day's first transactions.

The company's response was fast and correct on the substance. Customer money and data were never at risk. Granted. But custody and access are two different things, and outages only ever test the second one.

Worth knowing about the architecture: europe-west2 spans three availability zones, and that spread is the redundancy story Google sells. A regional incident means the redundancy didn't apply the way the diagram promised. One provider, one region, one bad morning, and a lot of people locked out.

Scale makes it worse. Revolut serves somewhere north of 50 million customers globally, and the UK is its home market. This wasn't a niche app wobbling. It was a systemically visible fintech, and the failure reached crypto tabs and payment rails at the same time.

The Cloud Is the Chokepoint

Here's what gets lost in the coverage. Bitcoin didn't blink during that window. Neither did Ethereum. Blocks kept coming every 10 minutes and every 12 seconds, roughly, while the front door stayed jammed.

So the failure wasn't crypto. It was the interface sitting on top of it. And that's the part proponents tend to skip, because it undercuts the be-your-own-bank pitch when the bank turns out to be a login screen bolted to a hyperscaler.

Admittedly, the same critique lands on traditional banks, which lean on the same clouds and fold just as fast when a region goes down. The question worth asking: if a single region of a single provider can shut millions of people out of their money for hours, how much concentration risk is everybody quietly holding?

What I'd Actually Do

Here's my strong opinion, and it won't be popular with marketing departments. The biggest obstacle to mainstream crypto adoption isn't the SEC, the FCA, or anyone's rulebook. It's uptime. Nobody recommends a payments app to a friend because it failed gracefully.

My practical take: if you keep meaningful crypto on a centralized platform, treat access as a separate risk from custody. Not your keys, not your coins is the old line. The newer one is that your keys don't help much when you can't reach the app that holds them.

Self-custody fixes the access problem and creates a dozen new ones. Lost seed phrases. Phishing. Relatives who don't know what a wallet is. I'm not going to pretend the tradeoffs are simple, because they aren't.

What to watch next: whether Revolut and Google publish a proper postmortem, and whether regulators start pressing fintechs on single-provider dependencies. History suggests otherwise, though an outage that touches card rails has a way of focusing minds faster than any consultation paper.