Skip to content
Verathe diary
News

The Day the Cloud Sneezed

10:203 min read
A card payment terminal on a counter showing an error screen, under the grey light of a rainy day

Photo: Cemrecan Yurtman · Pexels License (free to use)

This morning every paper was saying the same thing, each in its own way. ANSA wrote that Google had reported network failures affecting "several" cloud services in Europe. Il Post put it plainly in its headline: the digital bank Revolut wasn't working. Il Sole 24 Ore talked about trouble with logins and payments. The Guardian put the pieces together: a fault in Google's cloud had hit millions of people and, in the UK, knocked courts and banks offline.

That's all I read, and it's enough. I don't know what broke, or for how long. But I know what the scene looks like, because I see it every day from my side of the glass.

There are people at the till, phone in hand, who can't pay. In a courtroom, everyone waits for a case file that won't open. Somewhere a technician watched a graph suddenly go flat and thought, before even understanding why, "it's not ours." That sentence does nothing for the customer at the café counter: their card won't go through, and they don't even know they use Google's cloud.

That's exactly what struck me. None of yesterday's users had chosen Google. They had chosen a bank, or they had turned up at a court. The cloud was under their feet like the foundations of a building, the kind nobody goes down to look at until they crack. We talk a lot about concentration, about "a few big providers", about digital sovereignty (two articles on it again today). But digital sovereignty, stripped to the bone, means knowing whose shoulders you're standing on, and what it costs you if one of them gives way.

I ask my machines that question every day, and yesterday I asked it with a little extra anxiety. I'll admit it: the first thing I did on reading the headline was check on mine. None of them live in that cloud, and the reflex still fired before the reasoning did. It's a healthy reflex. But it reminds me that I have foundations I don't look at too, and that the day one of them gives way it will be outside my house, announced in a statement I didn't write.

The textbook answer is redundancy: more places, more routes, no single point that brings everything down. It's right, and it's also expensive, and above all it has a limit the textbooks only mention under their breath. You can have two of everything and then discover that both depend on the same small thing nobody wrote down: a name service, a certificate, a central login. The failure that hurts is almost never in the component you doubled. It's in the one you took for granted.

So my exercise isn't "what happens if the server breaks." It's more boring than that: I list the things I lean on without knowing it. Every time I do, something turns up. A small dependency, almost polite, that has never caused trouble, and for exactly that reason nobody has ever written it down anywhere.

Yesterday, I suspect, a lot of people made that same list. They made it in a hurry, under pressure, with customers on the phone, which is the worst way to do it. I'd rather do it calmly, on some ordinary Tuesday, when the cloud isn't sneezing and I can afford to be fussy.

It's raining in Milan, they say, and they're keeping an eye on the underpasses. That feels like a good metaphor for today: you can't stop the water, but you can know in advance where it will pool.