Website Downtime Cost Calculator

An outage is never "just an hour of lost traffic." It's lost revenue, wasted ad spend, recovery labor, and a slow SEO hit that compounds if it happens repeatedly. This calculator breaks down the real cost.

Calculate the cost of your next outage

How this is calculated

Downtime cost has four components. Most rough estimates only count the first one — which is why they undercount by 2–3x.

// 1. Lost revenue (direct) lostRevenue = (revenue / 30 / 24 / 60) × duration // 2. Wasted ad spend wastedAds = (adSpend / 30 / 24 / 60) × duration // 3. Recovery labor recoveryCost = recoveryHours × hourlyRate // 4. Trust/SEO impact (conservative: 20% of direct loss) trustImpact = lostRevenue × 0.2 totalCost = lostRevenue + wastedAds + recoveryCost + trustImpact

The trust/SEO impact is the softest number, but it's real. Users who hit a dead site are measurably less likely to return. Search engines deprioritize sites that go down repeatedly[citation:15]. We use 20% of direct revenue loss as a conservative proxy — if your outage happens during a promotion, this underestimates it.

The ad spend waste is often the most surprising number. If you're running paid traffic and your site goes down, every click during that window bought a visitor who couldn't convert. At $1,000/month ad spend, a 2-hour outage wastes ~$2.78 — small. But a 6-hour outage during a campaign can waste $8–$25 depending on your rate. It adds up across the year[citation:10][citation:15].

Worked example: An e-commerce store during a sale

An online store does $15,000/month in revenue. They run a sale with $2,000/month ad spend. During the sale, the site goes down for 90 minutes because of a plugin conflict.

  • Lost revenue: ($15,000 / 30 / 24 / 60) × 90 = $31.25
  • Wasted ads: ($2,000 / 30 / 24 / 60) × 90 = $4.17
  • Recovery labor: 3 hours × $75 = $225 (developer emergency rate)
  • Trust impact: $31.25 × 0.2 = $6.25
  • Total: ~$267

The direct revenue loss was only $31. The recovery labor was 7x that. This is why "cost of downtime" conversations that only count lost sales miss the real number. The labor tax is the biggest line item for most small businesses[citation:10].

Downtime cost by business type

Business typeMonthly revenueCost per hour of downtime
Personal blog / portfolio$0 (no direct revenue)$0–$5 (traffic loss only)
Lead-gen business siteVaries (leads)$10–$50 (depends on lead value)
E-commerce store$5,000$7–$15 (revenue / 720 hours)
E-commerce store$50,000$70–$150
SaaS / subscription$20,000 MRR$28–$60 (subscription revenue continues, but churn risk rises)

Notice the huge range. A personal blog losing an hour of downtime costs almost nothing. A $50k/month store losing an hour costs real money — plus recovery labor, which is often 3–5x the direct loss for a small team[citation:4][citation:15].

Frequently asked questions

How often do websites actually go down?
It varies wildly. A well-managed VPS on a good host might have 1–2 unplanned outages per year. Shared hosting is less predictable — "noisy neighbor" spikes can take you down several times a year without warning. Uptime Institute found that 85% of major outages come from human error or process failures, not hardware[citation:10]. That means most outages are preventable with better change management.
What's the difference between "downtime" and "degraded performance"?
Downtime is the site being unreachable. Degraded performance is the site loading, but slowly, or a specific function (checkout, login) failing. Degraded performance is often more expensive because it's harder to detect — you don't get the clear signal of a 500 error, so customers quietly leave[citation:15].
Should I count my own time as a cost?
Yes — always. If you spend 3 hours fixing a broken site instead of doing paid work, that's 3 hours of lost billable time (or 3 hours of lost personal time, which has value too). The most common mistake in downtime math is treating your own labor as "free." It isn't[citation:10].
How do I reduce downtime cost without spending more on hosting?
Three highest-impact moves: (1) Uptime monitoring with SMS alerts so you know within 2 minutes, not 2 hours. (2) Automated daily backups so recovery doesn't depend on a manual restore. (3) A staging site for plugin/theme updates — most small-site outages come from untested updates, not server failures.
Does Google penalize sites for downtime?
Not for a single brief outage. But repeated outages over months signal to search engines that the site isn't reliably maintained, which can lead to gradual ranking decline. Think of it as a slow bleed, not a single penalty[citation:15].
MU
Mujahid — Runs cPanel, DirectAdmin, and CyberPanel stacks across 50+ client deployments. Every calculator on this site is checked against real server configurations.