Michael PatelIn the past week alone, X (Twitter) suffered two significant outages — on 18 and 23 March 2026 — while the National Lottery app went down on 24 March, and Downdetector registered thousands of reports across multiple UK-critical services. When nearly every platform in your stack can fail in a single week, the question is no longer "will my tools go down?" but "what happens to my business when they do?"
The week that broke UK tech trust
The 18 March outage of X lasted 57 minutes, with around 5,000 UK users reporting issues at peak. Small and medium businesses that rely on X for customer service or marketing found themselves entirely offline. The National Lottery app outage on 24 March, with hundreds of reports surging around 11:30am BST, is a reminder that consumer-facing platforms are just as vulnerable. Downdetector's own traffic spiked — users turning to the site to check whether an outage was real or a problem on their end.
These are not isolated incidents. According to the UK National Cyber Security Centre, service disruptions from third-party providers are among the top five risks for British businesses in 2026. The problem is systemic: businesses have become entirely dependent on cloud-based tools, yet few have documented what to do when those tools disappear.
What UK businesses are actually risking
Every hour of downtime costs money. A 2025 survey by IT trade body techUK found that the average cost of unplanned downtime for a UK SME is £3,800 per hour. For e-commerce businesses, that number is considerably higher. Yet only 38% of UK SMEs have a formal business continuity plan that includes third-party software failure.
The UK government's NCSC publishes guidance on cyber resilience and business continuity, recommending that all organisations — even small businesses — document which systems are critical, identify fallback options, and test their recovery procedures at least annually.
What an IT specialist would tell you to do right now
A qualified IT consultant can assess your current tech stack and identify single points of failure — the services where a 1-hour outage would stop your entire operation. They can then help you build a realistic continuity plan. Here is what that typically involves:
1. Map your critical dependencies. Which tools are essential for revenue? Payment processing, email, customer database, project management? List them in order of business impact.
2. Identify redundancy options. For each critical service, what is the fallback? A second payment processor? A local backup of your CRM data? A phone number customers can call when chat is down?
3. Document and test. A continuity plan that exists only in someone's head is not a plan. It must be written, accessible offline, and rehearsed.
4. Monitor proactively. Tools like Downdetector provide public status, but a dedicated monitoring solution (UptimeRobot, Better Uptime, or similar) alerts you within minutes of a service failure — before your customers notice.
The hidden cost: customer trust
Beyond immediate revenue loss, repeated outages damage something harder to quantify. Customers who cannot reach you during a service failure do not always come back. They move to a competitor who was available. According to a 2025 Zendesk UK report, 61% of consumers say they would switch to a competitor after just one poor experience linked to a service outage.
An IT specialist can also help you communicate proactively during outages — setting up a simple status page, configuring automated email responses, or routing requests to a backup channel. This kind of preparation costs far less than the customer churn that follows a badly managed downtime.
We've written previously about why Discord outages keep hitting UK businesses hardest and how X going down exposes social media dependency risks — both relevant reading if you rely on these platforms.
Cloud-first was supposed to be more reliable — what went wrong?
The promise of cloud computing was simple: infrastructure managed by specialists, with built-in redundancy and 99.9% uptime guarantees. In practice, those guarantees are based on individual platform availability, not on the whole ecosystem of tools your business depends on. When X goes down and your entire customer support workflow lives on that platform, the 99.9% uptime of your email provider is irrelevant.
The March 2026 outages are part of a broader pattern. The consolidation of internet infrastructure around a handful of major platforms — Amazon Web Services, Google Cloud, Cloudflare, a few social networks — means that failures cascade in ways that were unimaginable ten years ago. A routing issue at Cloudflare can take down hundreds of SaaS products simultaneously. An authentication failure at Google can lock you out of Gmail, Drive, and every app that uses "Sign in with Google."
IT specialists increasingly recommend a "distributed resilience" approach: deliberately spreading your dependencies across different infrastructure providers, so a single failure cannot cascade across your entire stack.
What to do today
You do not need to wait for the next Downdetector spike to take action. Start with a simple audit: list every piece of software your business uses in a week. Mark which ones, if they failed for two hours, would stop you working entirely. That list is your business continuity priority list.
An IT consultant on Expert Zoom can help you go further — reviewing your infrastructure, recommending low-cost redundancy options, and building a written continuity plan that actually works. The next outage is coming. The question is whether your business will be ready for it.
