Skip to content
Uptime targets

99.5% uptime

99.5% uptime allows 3h 36m of downtime in a 30-day month and 1d 19h 48m in a year. Per day that is 7m 12s; per week, 50m 24s. Here is what fits in that budget, who promises 99.5%, and how to measure whether you're meeting it.

How much downtime is 99.5%?

Uptime is the share of time a service answers. The remaining 0.5% is the downtime budget, and it only looks small until it's written in minutes. The month figure uses 30 days; the year uses 365.

PeriodAllowed downtime
Per day7m 12s
Per week50m 24s
Per month (30 days)3h 36m
Per year1d 19h 48m

What 99.5% means in practice

Three and a half hours a month fits one bad incident, for example a server that needs a reboot and a restore, plus a few short blips. Two bad incidents and you've missed it. On a single server with no failover, 99.5% is roughly what careful operation and quick reaction achieve.

Spread evenly it's 7 minutes a day, which is about one deploy that goes wrong and gets rolled back, every day.

Who promises 99.5%

99.5% appears in the SLAs of some shared and managed hosting plans, and as the floor for single-instance (no redundancy) offerings from cloud providers, where a planned maintenance reboot is expected now and then.

It's also a realistic promise for a small team running one application server: honest, and achievable without duplicating everything.

How to measure it

Uptime is only a number if something is measuring it from outside, often enough to see short outages. heyUptime checks every 30 seconds (60 on Starter), confirms a failure with a second check before counting it, keeps 90 days of history on the status page, and sends a weekly summary with the uptime percentage per monitor. That's the figure to compare with 99.5%.

To turn any percentage into minutes, or minutes into a percentage, use the uptime calculator.

  • Checks every 30 to 60 seconds; shorter outages than that can't be seen by any external monitor.
  • Confirmed failures: a single slow response doesn't count as downtime.
  • Maintenance windows are recorded but not counted as outages on the status page.
  • The weekly summary reports uptime and response time per monitor for the week.

Is 99.5% enough for you?

In short: 99.5% is a fair target for a small business site on a single server. If downtime costs you money by the minute, aim one step higher.

The budget is big enough that most of it is spent on slow detection, not slow repair. Checks every 60 seconds with a confirmed alert mean you start fixing within two minutes, and a 90-day uptime history shows whether you're actually inside the budget or just assuming.

Questions

Is 99.5% uptime good?

It's acceptable for a small business site or a single-server app. It allows 3h 36m of downtime a month. Online shops and SaaS products usually aim for 99.9%, which cuts that to 43 minutes.

How much downtime is 99.5% per month?

3 hours and 36 minutes in a 30-day month; 50 minutes 24 seconds a week; 7 minutes 12 seconds a day.

How much downtime is 99.5% per year?

1 day, 19 hours and 48 minutes: just under two days.

See it on your own site.

heyUptime checks every 30 seconds, confirms before alerting, and tells you why it's down in plain words. Free for 14 days, no card.

Start watching free

Updated October 8, 2026.