TL;DR
- An hour of downtime costs a micro SMB under 25 employees around $100,000, or $1,670 per minute (ITIC, 2024).
- Across all company sizes, Splunk and Oxford Economics put the 2026 average at $15,000 per minute, with Global 2000 losses up 50% in two years to $600 billion a year.
- Hourly cost varies by an order of magnitude between sectors. The table below breaks it down.
- Six costs surface after recovery: lost revenue, SLA penalties, team overhead, customer churn, roadmap slippage, and reputation damage.
- Five conditions cause most preventable SMB outages: undocumented code, unowned legacy systems, deployments with no rollback path, unmonitored third-party dependencies, and support split across vendors.
- A self-audit checklist at the end shows where your own exposure sits.
When software fails, the business takes the hit—immediately and across the board.
Operations stall. Revenue slips. Customer trust erodes. In regulated industries, compliance risk increases. None of that is a technical detail. It’s a board-level concern.
For small and midsize businesses, the impact is often worse. They rarely have dedicated support teams, formal escalation processes, or mirrored infrastructure. Many run on legacy systems with limited documentation and rely on part-time contractors or one-person IT setups. When something breaks, there’s often no clear owner—and no quick fix.
So the question is a budget question: how much does an hour of downtime cost your business? Here are the benchmarks.
How Much Does IT Downtime Cost a Small Business?
An hour of downtime costs a micro SMB under 25 employees around $100,000, or $1,670 per minute, according to ITIC. The figure climbs with every server and revenue-critical application in the blast radius. Across all company sizes, Splunk and Oxford Economics put the 2026 average at $15,000 per minute, and aggregate losses for the Global 2000 rose 50% in two years to $600 billion a year. Downtime rarely appears in budget planning, which is why the number surprises people the first time they calculate it.
How Much Does One Hour of Downtime Cost?
Let’s start with the broad view:
- 90% of firms say an hour of downtime costs them over $300,000
- 41% of enterprises report hourly downtime costs between $1 million and $5 million
- Even among SMBs (20–100 employees), 57% say an hour of downtime costs up to $100,000
If you’re a micro SMB (e.g., <25 employees), that still translates to $1,670 per minute or $100,000 per hour—and that’s considered conservative.
- $16,700 per minute is standard when 10+ servers and core applications are affected
- The average across industries has reached $5,600 per minute (or ~$336,000/hour)
These are survey figures from companies that measured the loss. They apply to anyone running production systems without a support structure behind them.
What Does Downtime Cost by Industry?
Some sectors feel the impact of downtime more acutely than others. Below are benchmarks for business downtime costs by industry based on real-world data.
In the automotive sector, downtime can exceed $50,000 per minute, or $3 million per hour, due to stopped production lines and delayed deliveries. In manufacturing, businesses face an average of 800 hours of downtime per year, costing $260,000 per hour.
In healthcare and finance, the stakes include not just lost revenue—but regulatory penalties, patient safety, and litigation.
The Hidden Ripple Effects of Downtime
Six costs surface after recovery: lost revenue, SLA penalties, team overhead, customer churn, roadmap slippage, and reputation damage. Most companies track the outage itself, fix it, and never price the aftermath.
Here’s what happens after systems go down:
- Revenue stops – Orders, payments, and transactions pause. No system, no cash flow.
- SLA penalties – If you promised uptime, expect credits, discounts, or legal tension.
- Team overhead – Your best people drop their work to triage, debug, and clean up.
- Customer churn – Every hour offline costs you users. Some don’t come back.
- Roadmap slips – Recovery eats into roadmap time. Releases get pushed.
- Reputation takes a hit – You get labeled as unreliable. It sticks.
If you're not tracking these ripple effects, you're underestimating the business cost of outages.
Implementation Tips
- Use this table in post-mortems: Go beyond root cause. Ask what each column cost you.
- Turn rows into OKRs: Assign ownership across engineering, product, support, and customer success.
- Run quarterly downtime impact audits: This builds the case for preventative investment—without waiting for the next crisis.
What Causes Downtime in SMB Environments?
Five conditions account for most preventable SMB outages: undocumented code, unowned legacy systems, deployments without rollback paths, unmonitored third-party dependencies, and support split across vendors. Each one starts long before the crash.
Take the codebase. Over time, it fills with fragments no one owns. Scripts with unclear purposes. API calls no one remembers writing. When things break, you waste hours figuring out what you're even looking at.
Then there’s legacy software—critical systems everyone’s afraid to touch. They're fragile, undocumented, and usually built by someone long gone. Teams avoid them until they fail under pressure or during routine maintenance.
Even in modern stacks, updates often go live without rollback plans. When something breaks, recovery becomes trial-and-error. Meanwhile, the system stays down, and customers start to notice.
Many systems also rely on third-party services—payments, email, auth—but no one monitors them. If a vendor fails, you fail too. And without alerts or fallback logic, you hear about it from users first.
And finally, support is often scattered. Freelancers, agencies, and internal staff each own a piece of the puzzle. But when something goes wrong, no one has full visibility—or accountability.
These aren’t edge cases. They’re routine. And they’re exactly where most preventable downtime begins.
Each of these creates friction during recovery and increases the chance of outages in the first place.
Implementation Guidance:
- Use this table in a quarterly system health review or as part of onboarding a new tech lead.
- Each “What to Do” action is designed to be implementable with minimal resources—no major platform shifts required.
- These patterns also double as root cause audit checkpoints when downtime occurs.
Checklist: Are You at Risk of a Business-Crashing Outage?
Use this as a quick self-audit. If you check more than a few boxes, your business is likely carrying silent operational risk—and it's just a matter of time before it turns into a visible outage.
How Do You Reduce Downtime Costs?
The cost of IT downtime in 2026 is a hard number. And for many SMBs, it’s hiding in plain sight.
The companies that stay resilient do three things:
- Quantify what a minute of downtime costs them
- Map their weakest points and operational gaps
- Shift investment toward prevention—not just resolution
Support and maintenance aren’t cost centers. They’re insurance against revenue loss, customer churn, and team burnout.
If you’re still firefighting incidents, running on legacy code, or struggling with visibility—you’re not alone. But the path forward is clear: build systems that are monitorable, maintainable, and resilient by design.
That is how you reduce downtime costs and keep the business moving when it counts.
MEV is a custom software development company. We run application maintenance and support for SMBs with production systems on legacy code, and our Software Health Check maps where the outage risk sits before it costs you an hour.
This artilce is for SMB owners and engineering leads who need a dollar figure for downtime before they can make the case for a maintenance budget. It gives you the published benchmarks by company size and sector, plus the six costs that land after systems come back up. The checklist at the end helps you locate your own weak points.The figures come from ITIC and Splunk survey data, which records what respondents estimate their losses to be. Use them as a starting range, then run the numbers against your own revenue per hour.
