Skip to content
Uptime targets

99% uptime

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

How much downtime is 99%?

Uptime is the share of time a service answers. The remaining 1% 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 day14m 24s
Per week1h 40m 48s
Per month (30 days)7h 12m
Per year3d 15h 36m

What 99% means in practice

Seven hours a month is a whole working day of outages, or a two-hour incident every weekend. A site at 99% is down often enough that regular visitors have seen it: on a shop, that's a lost sale a week; on a SaaS product, it's the number a competitor quotes against you.

It is also the level a site reaches with no monitoring at all, because most outages last until someone notices. A single unnoticed Friday-night crash fixed on Monday morning uses about eight months of a 99% budget in one go.

Who promises 99%

Almost nobody promises 99% in writing, because it's easy to beat; cheap shared hosting that offers no SLA at all usually lands around here in practice. Free tiers and hobby plans on platform-as-a-service providers are typically "best effort", which over a year often works out near 99%.

Where you do see 99%, it's for non-critical internal tools, beta products, or a contractual floor below which a refund starts.

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%.

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% enough for you?

In short: 99% is enough for a personal site or an internal tool nobody pays for. For anything with customers, aim for 99.9% and measure it.

The difference between 99% and 99.9% is not nine times the engineering; it's noticing outages in minutes instead of hours. A monitor that checks every 60 seconds and alerts after a confirmed failure turns a four-hour outage into a twenty-minute one, and that alone takes most small sites from two nines to three.

Questions

Is 99% uptime good?

No, not for a business. It allows 7h 12m of downtime a month and 3d 15h 36m a year. It's acceptable for a hobby site or an internal tool; anything with customers should aim for 99.9% or better.

How many hours of downtime is 99% per month?

7 hours and 12 minutes in a 30-day month, 1 hour 40 minutes a week, and 14 minutes 24 seconds a day.

How many days a year is 99% uptime?

3 days, 15 hours and 36 minutes. That's 1% of 365 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.