What it means
The measure is deliberately simple: take the hours something should have been running, divide the hours it was not running by that figure, and express the result as a percentage. The judgement lies entirely in what counts as scheduled time and what counts as downtime.
It matters because availability is often contractually promised and financially penalised. Hosting providers, payment processors and logistics operators sign service level agreements that specify an availability target, and missing it triggers service credits, refunds or in serious cases the right to terminate.
In practice teams split downtime into planned and unplanned. Planned maintenance windows are usually excluded from the calculation because customers were warned, while unplanned outages count in full; arguing about which bucket an incident falls into is a common source of friction between suppliers and their clients.
The percentage is also a manufacturing staple, where it feeds into overall equipment effectiveness alongside performance and quality. A production line that is available 96% of the time but only running at 80% of rated speed has a very different problem from one that is fast but frequently stopped.
The nuance worth remembering is that headline availability figures hide when the outage happened. Thirty minutes down at three in the morning is not the same as thirty minutes down during a checkout peak, so mature organisations weight downtime by transactions or revenue lost rather than by the clock alone.
Severity is the other definition that needs settling in advance. Many teams count partial degradation, such as a service that still responds but takes ten seconds to load a page, as fractional downtime rather than ignoring it entirely.
Agreeing that rule before an incident avoids a long argument afterwards about whether slow counts as down.
In practice
Real-world examples.
Example
A regional bakery tracks downtime on its main packing line and finds it sits at 4.5% of scheduled hours, most of it caused by changeovers between product sizes. Reordering the production schedule to group similar sizes cuts the figure to 2.8% without any capital spend.
Example
A software company publishes a monthly status page showing 99.98% uptime. When a database failure pushes one month to 99.6%, the account team proactively issues service credits to its twelve largest customers before any of them ask.
Example
A logistics operator measures downtime on its automated sorting equipment and discovers that 70% of the lost hours come from a single conveyor section. Replacing one motor removes most of the problem and pays for itself within a quarter.
Think of it
“Downtime shows how much time your equipment or systems are not working-unavailability rate.
Formula
Calculation
Formula: Downtime % = (Downtime hours / Scheduled hours) x 100. Uptime % = 100 - Downtime %.
Worked example. A payments platform runs continuously through a 30-day month, so scheduled time is 30 x 24 = 720 hours. Two unplanned incidents take it offline for 3.0 hours and 2.4 hours, a total of 5.4 hours. Downtime is 5.4 / 720 x 100 = 0.75%, so uptime is 99.25%. The customer contract promises 99.9% availability, which allows only 720 x 0.001 = 0.72 hours, or about 43 minutes, of unplanned downtime. The platform has breached its commitment, and the agreed remedy is a service credit of 10% of the $40,000 monthly fee, which is $4,000.Case study
Seen in the real world.
What follows is an illustrative, fictional case. Cedarvale Fulfilment, an invented third-party warehousing business, promised its retail clients that its order-picking systems would be available 99.5% of scheduled hours. For two years nobody measured it properly, because the operations team logged stoppages in a shared spreadsheet that was rarely reconciled.
When a new operations director standardised the definition and started counting, the true figure for the previous quarter turned out to be 97.9% downtime-adjusted availability, or roughly 2.1% downtime against a permitted 0.5%. Three clients were entitled to credits worth $86,000 in total, and one used the breach as leverage in a renewal negotiation.
Cedarvale responded by separating planned maintenance from unplanned failure in its reporting and by weighting incidents against order volume. The revised picture showed that a handful of short outages during the evening dispatch peak were doing most of the commercial damage, which redirected the maintenance budget far more usefully than the headline percentage ever had.
Watch out
Common mistakes.
- Comparing downtime percentages between teams that use different definitions of scheduled hours, so one includes weekends and holidays while the other does not.
- Quietly reclassifying an unplanned outage as planned maintenance after the event to protect the reported figure.
- Treating a low percentage as automatically acceptable without checking when the downtime occurred and what it cost in lost orders.
Questions
People also ask.
How is downtime percentage different from uptime?
They are two views of the same number; uptime is simply 100% minus the downtime percentage over the same scheduled period.
Does planned maintenance count as downtime?
Usually not, provided the maintenance window was agreed in advance and falls outside the contracted service hours, but the contract should say so explicitly.
What does 99.9% availability actually allow?
Roughly 43 minutes of unavailability in a 30-day month, or about 8 hours 46 minutes across a full year.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%