Performance5 min read

The real cost of downtime (and how to never pay it again)

When your site goes down, no invoice arrives. That’s the trick of it. A broken delivery truck has a repair bill you can read; a down website just quietly doesn’t make the money it was going to make, and the books never show a line item for it. So let’s write the invoice that never arrives — because downtime bills you in five currencies at once.

Currency one: the sales that didn’t happen

The arithmetic is blunt. Take your monthly online revenue, divide by 730 hours, and that’s roughly what each hour of downtime costs at minimum — before accounting for the fact that outages love peak traffic, because peak traffic is what knocks over weak hosting. A store doing $40k a month loses about $55 every hour it’s dark on average; go down during your best sales window and multiply accordingly. We’ve watched an e-commerce client’s “occasional timeouts” turn out to be costing more per month than proper hosting and care would have cost per year.

Currency two: the customers who don’t come back

An hour of downtime doesn’t cost you an hour of customers. Some fraction of the people who hit an error page form a one-word opinion — “sketchy” — and buy from the competitor whose site loaded. You paid to acquire that click. The refund never comes. For businesses where trust is the product — healthcare, finance, anything with a checkout — an error page is a billboard advertising unreliability, displayed to exactly the people you most wanted to impress.

Currency three: rankings

Google notices. Brief blips are forgiven; a pattern of failed crawls and slow responses is not. Pages get crawled less, rankings drift down, and the organic traffic you spent years earning erodes — an invoice that arrives months later, with no return address, payable in traffic you’ll have to win back the hard way.

Currencies four and five: panic rates and your weekend

Emergency fixes are the most expensive labor in the industry — whoever’s available, at urgency pricing, learning your site from scratch while it’s on fire. And the founder-hours are worse: the Saturday spent refreshing the host’s status page, the adrenaline, the week of distraction afterwards. Ask anyone who’s lived a real outage which currency hurt most; it’s rarely the first one.

What never paying it again looks like

Here’s the encouraging part: downtime is mostly a solved problem. The unglamorous checklist:

  • Hosting sized for your reality — managed, with headroom for your best day, not your average one.
  • Monitoring that pages a human — minutes-not-days detection. Most “six-hour outages” were ten-minute fixes discovered five hours and fifty minutes late. (Here’s what real monitoring involves.)
  • Disciplined updates — since botched updates and unpatched holes cause a huge share of self-inflicted outages.
  • Tested backups — restore drills, not restore hopes, so the worst case is measured in minutes.
  • One owner — a team that knows the site before the fire, so response starts at “fixing” instead of “orienting.”

We’ve run this playbook for a decade on sites where downtime genuinely matters — including LA Progressive, a political news site whose traffic spikes hardest on election nights, precisely when failure would be most visible. The platform holds because the boring work happens every week of the year, not the week of the election.

Write your own outage biography

Before deciding any of this applies to you, spend ten minutes on your actual history. When did the site last go down or noticeably degrade — and how did you find out? (If the answer involves a customer, that’s finding number one.) How long did detection take versus repair? Who fixed it, what did they charge, and what did the week around it look like for you? Most businesses have this story; almost none have written it down, which is why the same story repeats.

The pattern across incidents matters more than any single one. Detection delays mean a monitoring gap. Repeat offenders — the same plugin, the same host, the same fragile checkout — mean a maintenance gap. Fixes that always require finding a new stranger mean an ownership gap. Your past outages are a free diagnostic of exactly which insurance you’re missing; the only mistake is not reading them.

The comparison worth making

Add up one realistic bad incident in all five currencies — lost sales, lost customers, ranking damage, emergency rates, your hijacked week. Now compare it to a year of flat-rate care that makes the incident dramatically less likely and dramatically shorter if it happens anyway. For any site with real revenue, it isn’t close.

Uptime isn’t a feature. It’s the foundation everything else stands on — and it’s purchasable. If your site has been wobbling, get a free systems review and we’ll tell you exactly where the next outage is hiding.

The newsletter

Stop firefighting, one email at a time.

Plain-English notes on keeping your platform fast, stable, and out of your way. No fluff, ~2x a month — join 2,500+ founders.