TimecardPastely

What does 99.9% actually allow?

See the downtime each uptime target allows, then enter an outage to check how much of your budget is left.

99.9% allows 43m 50s a month. That's 8h 45m a year.

Per day
1m 26s
Per week
10m 5s
Per month
43m 50s
Per quarter
2h 11m
Per year
8h 45m

31m 50s of budget left

99.973% actual uptime

How the nines work

Allowed downtime = period length × (1 − uptime ÷ 100)

Each extra nine cuts allowed downtime by ten. 99.9% allows about 43 minutes a month, and 99.99% allows about 4 minutes, which is less time than it takes most people to notice an alert and open a laptop.

Error budgets

Actual uptime = (period length − downtime) ÷ period length × 100

An error budget treats allowed downtime as something you can spend. While there's budget left, you can ship riskier changes. When it's gone, the usual advice is to prioritise reliability until the period resets.

Don't learn about downtime from your customers.

Spikely watches requests, errors and signups together, so a sudden drop reaches you first, with what changed around it.

3 days free on yearly · iPhone, iPad, Mac and Apple Watch

Questions, answered plainly.

An average month of 30.44 days, based on a 365.25-day year, so the months add up to a year. Your provider's SLA may define it differently, so check the contract if money depends on it.

No. An SLA is a promise, usually with credits if it's missed. Your actual uptime is what really happened, and a provider's status page may not count every incident you felt.

If your app needs two services to both be up, their uptimes multiply. Two 99.9% services give you about 99.8%, so your promise usually can't be stronger than what you depend on.

No. The calculation runs in your browser, and your numbers aren't sent anywhere.

More free tools