What does internet downtime cost a business?

Most businesses choose a broadband or connectivity package the same way they choose a phone tariff: by looking at the monthly price and picking the one that feels reasonable. That works fine right up until the connection goes down on a busy morning, the card machine stops, the phones go quiet, and a room full of paid staff sit waiting for the internet to come back. At that point the monthly price stops being the number that matters.

This guide is about that hidden number: what an hour, a morning, or a full day offline actually costs your business, and why that figure should shape the connectivity you buy. It isn't a scare story. Outages are uncommon on a well-run line. The point is simply that the cost of being offline is usually larger and more lopsided than people expect, so it deserves a place in the decision alongside the headline price.

Internet downtime usually costs far more than the price difference between basic connectivity and resilient connectivity. Lost sales, idle staff, missed calls, failed card payments, and delayed customer work can add up quickly, which is why businesses should judge connectivity by risk and recovery time, not just monthly price.

What does internet downtime actually cost a business?

The cost of an outage is rarely one thing. It is a stack of smaller costs that all hit at once, which is why a single bad hour can feel disproportionate. The biggest items are usually idle staff time, lost sales or transactions, missed calls and enquiries, and customer work that slips past its deadline.

Idle staff time is the easiest to overlook because it doesn't show up as a refund or a lost order. If ten people who depend on cloud apps, email, and hosted phones cannot work, you are still paying their wages while nothing gets done. Lost sales are sharper still for any business that takes payment online or in person: a card terminal that cannot reach the bank, an online checkout that won't load, or a booking system that times out all turn directly into revenue you never see.

Then there are the second-order costs that don't fit neatly on a spreadsheet. A customer who can't get through on the phone may simply call a competitor. A delayed delivery or a missed deadline can cost goodwill that is worth far more than the hour it took to recover. None of this is meant to alarm you. It is meant to show that the real cost of downtime is broader than the obvious lost sales, and that is exactly why it tends to be underestimated.

Which types of business lose the most when the internet drops?

Downtime does not hit every business equally. The cost depends on how tightly your day-to-day operation is tied to the connection, and on whether an outage hits revenue or just productivity. A handful of patterns stand out.

• Retail and hospitality. Card payments, tills, and bookings all run over the line. An outage during a busy lunch or a Saturday afternoon converts straight into lost takings, and customers rarely come back later to pay.
• Phone-led service teams. If your hosted phones, helpdesk, or sales line run over the same connection, an outage means missed calls and enquiries that quietly walk to a competitor.
• Professional and creative firms. Accountants, agencies, and consultancies live in cloud apps and large file transfers. Downtime stalls billable work and pushes deadlines, which costs both time and trust.
• Multi-site and remote-dependent businesses. When several locations or home workers all rely on a single hub line, one outage stops everyone at once, multiplying the idle cost.

If your business sits in one of these groups, the case for resilient connectivity is much stronger, because the cost of an outage is concentrated and immediate. A low-dependency business that can work offline for an hour will reach a very different conclusion, and that is fine. The goal is to match the connection to the real risk, not to overspend on resilience you don't need.

Why is the monthly line price the wrong thing to optimise?

The monthly price is easy to compare, which is exactly why it dominates the decision. Two connections sit side by side, one is a few pounds cheaper, and the cheaper one wins. The trouble is that the monthly price tells you almost nothing about how often the line will drop, or how quickly it will come back when it does.

Those two factors, how often and how fast, are where the real cost lives. A connection that is a little cheaper each month but takes far longer to repair when it fails can end up far more expensive over a year once you count the lost trading. Optimising for the lowest monthly price is really optimising for the wrong variable: you are saving a predictable, small amount in exchange for an unpredictable, potentially large one.

A better way to frame the choice is total cost of connectivity: the monthly price plus the expected cost of the downtime that comes with it. Seen that way, paying a bit more for a more resilient line, or for a backup that keeps you running through an outage, often looks like the cheaper option overall. That is the case for products such as business broadband with proper support, rather than a consumer line bought on price alone.

How do uptime, MTTR, and backup connectivity reduce the risk?

There are three levers that shrink the cost of downtime, and it helps to keep them separate. The first is uptime, the share of time the connection is working. The second is repair speed, often measured as MTTR (mean time to repair), which is how long an outage typically lasts before service is restored. The third is backup connectivity, a second path to the internet that keeps you running while the main line is fixed.

Uptime and MTTR matter for a simple reason: your downtime cost is roughly the cost per hour offline multiplied by the hours you are offline. Higher uptime means fewer incidents, and a lower MTTR means each incident is shorter. A connection backed by a strong SLA (service level agreement) commits the provider to those numbers, which is what separates a business-grade line from a best-effort consumer one. The mechanics of how an SLA works are a topic in their own right, so we won't labour them here; what matters for this decision is that a committed fix time directly caps your worst-case downtime cost.

Backup connectivity attacks the problem from the other side. A 4G or 5G connection that takes over automatically when the main line drops means an outage becomes a brief wobble rather than a stoppage. For many businesses, the combination of a resilient primary line and a mobile backup is the sweet spot: rare outages, short ones, and a fallback that keeps the tills and phones alive even during the rare event.

When does downtime justify a leased line or failover?

The honest answer is that it depends on your downtime cost, which is why the calculation in the next section matters. As a rule of thumb, the more your revenue or billable work depends on the connection, and the less tolerant your customers are of being kept waiting, the stronger the case for serious resilience.

A leased line makes sense when uptime is genuinely business-critical: a dedicated, uncontended connection with a committed fix time, where you are paying for the guarantee as much as the speed. If a few hours offline would cost you thousands in lost trading, the higher monthly price is easy to justify. Adding mobile failover on top covers the rare case where even the leased line is interrupted.

At the other end, a small office that can pick up the phone, work offline for a while, and catch up later may be perfectly well served by a good business line with a 4G or 5G backup. There is no single right answer. The point is to let the size of your downtime cost decide, rather than reaching for the most resilient option by reflex or the cheapest one by habit. Home-based and hybrid setups have their own version of this trade-off, covered on our home office connectivity page.

How should a business estimate its own downtime cost?

You don't need a complicated model. A back-of-envelope figure is usually enough to make the decision clear. The aim is a defensible cost per hour offline, which you can then compare against the price difference between a basic line and a resilient one.

A simple way to estimate it, using illustrative figures for example:

• Idle staff cost. Loaded cost per hour per person, multiplied by the number of people who cannot work offline. Roughly £25 per hour each for 10 people gives £250 an hour.
• Lost transactions. Average revenue per hour that flows through the connection. For a shop taking roughly £400 an hour in card sales at a busy time, that is £400 an hour at risk.
• Knock-on costs. Missed calls, delayed customer work, and goodwill. Harder to put a figure on, so treat it as a sensible buffer on top rather than a precise number.

Putting the first two together, this example business is looking at roughly £650 for every hour offline during a busy period. The table below shows how that scales, using the same illustrative figures.

The figures are illustrative, and your own numbers will differ, but the shape of the answer rarely changes: even a modest business carries a downtime cost that dwarfs the few pounds a month saved by buying connectivity on price alone. Once you have your own cost per hour, compare it against the monthly difference for a resilient line or a backup. If a backup that costs a small amount each month would have saved that £650 hour even once or twice a year, the decision tends to make itself. That, in the end, is the whole point: connectivity is worth judging by the cost of going without it, not by the figure at the bottom of the invoice.

Frequently asked questions