For a few hours recently, global cloud platform Cloudflare went down – and a noticeable chunk of the internet went with it.

Services stalled, platforms froze, and businesses were left dealing with failures they didn’t trigger and couldn’t control – from broken checkouts to lagging internal tools.

From the outside, it looked like the usual internet wobble. A quick refresh, a short wait, and most people moved on. Inside the organizations that depend on those upstream layers, the mood was very different.

Article continues below

Teams watched systems slow down or stop entirely, and it became clear – again – how easily a single fault in one provider can spill across the wider digital ecosystem.

And these incidents aren’t isolated.

Late last year, another Cloudflare issue hit – this time a configuration change that went wrong – and it took major platforms offline within minutes. Outages at global tech platforms and hyperscalers such as AWS have shown how disruption in one region can ripple outward at speed.

Even external events, like conflict in the Middle East, have knocked data centers offline and forced providers to reroute traffic under pressure. In addition, AI‑assisted changes have introduced unexpected instability.

The triggers vary, but the pattern is becoming familiar: one layer stumbles, and everything built on top of it feels the shock.

Why outages don’t stay contained

Most companies don’t think of themselves as heavily dependent on the likes of Cloudflare, AWS, or any other upstream provider in any meaningful way. In reality, they’re embedded across almost every part of modern digital services.

Today’s systems are built on stacked infrastructure: cloud platforms, routing and security layers, CDNs, authentication systems, and third-party APIs. Each layer adds capability, but also dependency.

When something breaks upstream, it doesn’t stay contained. It moves outward through those layers, affecting systems several steps removed from the original fault.

What catches people out is how far this travels. A failure in one provider doesn’t just hit its direct customers; it hits the platforms built on top of it, the tools those platforms rely on, and the businesses relying on all of them to operate. By the time the issue becomes visible, the blast radius is already far and wide.

Where the cracks show first

Payments tend to expose these failures faster than most. A single transaction touches a long chain of systems: cloud infrastructure, fraud engines, authentication services, and processing networks. If one link snaps, the impact shows up immediately. Transactions hang, checkouts stall, and customers abandon carts.

That has a direct business cost within minutes, or even seconds.

But payments aren’t uniquely fragile; they’re just where people feel the outage the hardest – it’s their money on the line. The same dependencies run through ecommerce platforms, SaaS tools, logistics systems, customer support and internal operations. Payments just make the problem impossible to ignore.

That’s what makes the concentration of infrastructure such a risk. A relatively small number of providers now sit at the core of a huge share of digital services. That scale brings reach and reliability, but it also means the impact isn’t isolated: when something goes wrong, it rarely affects just one company.

Planning for failure, not perfection

Despite all this, outages are still treated as ‘we’ll deal with it when it happens’ moments, instead of something you actively design for.

Redundancy gets weighed against cost; dependency mapping is incomplete, and continuity plans sit untouched. And the assumption persists that major providers 'don’t go down', even though recent history shows that they most definitely do, and they will again.

There’s another issue behind all of this, and it’s one most organizations don’t say out loud: they no longer control the infrastructure they rely on.

Over the past decade, companies have handed more of their core systems to hyperscalers and a mix of third-party providers. It’s been great for speed and scale. But the trade-off is obvious every time an upstream service wobbles.

When something breaks several layers above you, there’s very little you can do except wait and watch the impact roll downhill.

Most organizations already have frameworks that are meant to cover this. But when the internet goes down, it’s not security or compliance that gets tested: it’s availability. And that’s the part that has to hold up in the real world.

In financial services especially, there’s a quiet move toward hybrid setups: keeping the big clouds in play but adding regional or specialist providers as backup routes.

Part of that shift is down to geopolitics as much as technology. Most European businesses still run on US cloud and AI platforms, and that’s fine until global politics get jumpy. Banks in particular are asking a simple question: what happens if those services get caught up in a political row they have no control over?

When a single outage can knock out authentication, routing or payments across a whole region, having another route stops being a nice-to-have and starts being basic self-preservation.

Different organizations are moving at different speeds, whether because of regulation or risk. But the message is clear: staying online isn’t luck. It’s something you build for.

The pressure is only increasing

The conditions that make these incidents so disruptive (shared infrastructure, tightly connected systems, real-time digital services) aren’t going anywhere. If anything, they’re getting more intense.

So, the real question for businesses isn’t whether another outage will happen, it’s how exposed they are when it does – and how quickly that exposure turns into lost revenue, operational disruption, and customer frustration.

Given how the modern internet behaves, staying online isn’t luck; it must be designed for. So, remember… do the basics to soften the blow: backup routes, a clear view of their dependencies, and no hidden single points of failure waiting to trip you up.

We've featured the best customer experience (CX) tool.

This article was produced as part of TechRadar Pro Perspectives, our channel to feature the best and brightest minds in the technology industry today.

The views expressed here are those of the author and are not necessarily those of TechRadarPro or Future plc. If you are interested in contributing find out more here: https://www.techradar.com/pro/perspectives-how-to-submit

Chief Information Officer at Tribe.