Your website goes down at 9am on a Tuesday. When does your team find out?
For most businesses without active monitoring, the answer is: hours later, when a client emails to say they tried to reach you and got an error. Or when the sales team notices that inbound form submissions have stopped. Or — in the worst case — when someone notices the next day.
The 6-Hour Downtime Cost Model
Let's use conservative numbers. A business website generates 500 unique visitors per day. Of those, 2% complete a contact form — 10 leads per day, or roughly £500 in lead value at £50 per lead (conservative for most B2B services).
A 6-hour outage during business hours eliminates roughly 25% of the day's traffic — losing 2–3 leads. At £50 per lead, that is £100–£150 in immediate lost lead value.
But the direct lead loss is the smallest part of the cost.
ITIC's Global Server Hardware and OS Reliability research found that a single hour of downtime costs small businesses an average of $8,000–$74,000 depending on size and sector — a figure that includes lost productivity, customer impact, and recovery costs beyond just lost transactions.
The Costs Nobody Calculates
- PPC spend wasted: if you are running paid ads and your site goes down, every click during the outage is paid for and wasted. A £100/day Google Ads budget during a 6-hour window costs £25 in wasted spend, with nothing to show for it.
- Email campaign timing: if you sent an email blast to 2,000 contacts at 10am and your site was down until 3pm, the peak traffic generated by that campaign had nowhere to land.
- Sales call credibility: if a prospect checks your site during a discovery call and gets an error page, the trust and professionalism signals you are trying to establish evaporate immediately.
- SEO signal: Google crawls high-traffic sites frequently. A crawl during downtime returns a 503 error. Repeated 503s in Google's crawl data trigger ranking reviews. Sustained downtime — multiple hours across several occurrences — has measurable SEO ranking impact.
What Causes Most Unplanned Downtime
- Shared hosting environment failures — your site is on the same server as thousands of others, and a spike in traffic to a neighbouring site takes everyone down.
- Plugin update conflicts — an auto-update to a plugin or CMS core version that is incompatible with another plugin, causing a fatal error.
- SSL certificate expiry — a certificate that was not renewed automatically causes the browser to block access to the site with a security warning. This is entirely preventable.
- Server resource limits hit — a site experiencing unusual traffic (after a PR mention, a viral post, or a successful ad campaign) exceeds shared hosting limits and is suspended.
What Monitored Infrastructure Actually Provides
The standard in properly managed infrastructure is a 5-minute alert on downtime. This means: if your site goes down at 9am, your service provider knows by 9:05am. For production outages, the SLA should specify a 2-hour response time during business hours.
This turns a potential 6-hour undetected outage into a 2-hour managed incident — with most of the business impact eliminated.