Explainers · Explainer
What Is Uptime? A Plain Explanation

Short answer
Uptime is the share of time your website is available and responding to visitors, written as a percentage. A 99.9% uptime promise allows about 43 minutes of downtime in a 30-day month, or about 8 hours 45 minutes over a year. It is measured by an outside service that checks your site every few minutes and counts how many checks succeed.
Key takeaways
- Uptime is the share of time your site is available, usually written as a percentage.
- 99.9% uptime allows about 43 minutes of downtime in a 30-day month.
- Each extra nine divides the allowed downtime by ten, so 99.99% allows only about 4 minutes a month.
- An SLA is a contract with consequences for missing its target; an SLO is a target without one.
- Most hosting agreements exclude scheduled maintenance from the uptime calculation.
- A free outside monitor that checks every five minutes is enough for most small sites.
What is uptime?
Uptime is the share of time your website is available and responding to visitors, usually written as a percentage.
A site with 99.9% uptime was reachable for 99.9% of the measured period and down for the other 0.1%. The opposite number is downtime: the time your site was unreachable, returned errors, or failed to load. Uptime is the simplest health number for a website, and it is the one hosting companies advertise most.
The number only means something with a time window attached. “99.9% uptime” over a month is a different promise from 99.9% over a year, because the allowed downtime grows with the window. Our guide to what a good uptime percentage is for hosting looks at the same numbers from the hosting buyer's side.
How is uptime measured?
Uptime is measured by checking the site at regular intervals and counting how many checks succeed.
A monitoring service sends a request to your home page every few minutes and records whether it gets a valid response. Uptime is then the share of successful checks over the period, and downtime is the rest. The basic formula is: uptime percentage equals one minus downtime divided by total measured time, times 100.
The check interval matters. Jetpack's downtime monitor checks your site every five minutes, according to Jetpack's own support page, and emails the site administrators when it looks like something has gone wrong (Monitor your site's uptime and downtime).
A five-minute interval can miss an outage that lasts two minutes, and it can also report a site as down when it was only slow to answer one check.
What does 99.9% uptime actually allow?
A 99.9% promise allows about 43 minutes of downtime in a 30-day month, or about 8 hours 45 minutes over a year.
The arithmetic is simple: downtime equals the length of the period multiplied by one minus the uptime percentage. For a 30-day month, that is 30 days times 24 hours times 60 minutes times 0.001, which comes to 43.2 minutes.
The same calculation for each common level gives the table below, using a 30-day month and a 365-day year.
| Uptime | Allowed downtime per month | Allowed downtime per year | Common name |
|---|---|---|---|
| 99% | 7 hours 12 minutes | 3 days 15 hours | Two nines |
| 99.5% | 3 hours 36 minutes | 1 day 19 hours | Two and a half nines |
| 99.9% | 43 minutes 12 seconds | 8 hours 45 minutes | Three nines |
| 99.95% | 21 minutes 36 seconds | 4 hours 22 minutes | Three and a half nines |
| 99.99% | 4 minutes 19 seconds | 52 minutes 35 seconds | Four nines |
| 99.999% | 26 seconds | 5 minutes 15 seconds | Five nines |
Each extra nine divides the allowed downtime by ten, so the step from 99.9% to 99.99% is a tenfold improvement, not a small one. It is also far more expensive to deliver, which is why most small business sites aim for 99.9% rather than chasing five nines.
What is the difference between uptime, SLA, SLO, and SLI?
Uptime is the measurement, while SLA, SLO, and SLI are the three terms that describe how that measurement is promised and judged.
Google's Site Reliability Engineering book defines them clearly. An SLI, or service level indicator, is a carefully defined quantitative measure of some aspect of service, such as availability, the fraction of time a service is usable (Service Level Objectives).
An SLO, or service level objective, is a target value for that indicator, such as 99.95% availability. An SLA, or service level agreement, is a contract with your users that includes consequences if the SLOs in it are missed.
The book also notes that 100% availability is impossible, and that the industry commonly expresses high availability in terms of the number of “nines”: 99% is two nines and 99.999% is five nines, while Google Compute Engine's published target is 99.95%, or three and a half nines (Service Level Objectives).
The practical difference is what happens when the target is missed. If there is no stated consequence, you are looking at an SLO, not an SLA.
When a host misses an SLA, the usual remedy is a service credit, a percentage of that month's fee applied to a future invoice, rather than compensation for lost sales.
What counts as downtime?
Downtime is whatever the agreement says it is, so read the exclusions before you trust the percentage.
Most hosting agreements exclude scheduled maintenance from the uptime calculation, along with events outside the host's control, such as network outages upstream, DNS failures, and attacks on the site itself.
A host that promises 99.9% uptime can still take your site down for a planned maintenance window without breaking that promise, as long as the window was announced in advance.
Slow is usually not down either. Most agreements define availability as a successful response, not a fast one, so a site that takes 30 seconds to load can still count as “up” for SLA purposes.
That gap is why uptime alone never tells the full story, and why speed checks matter too. See our guide to how to test hosting speed before buying for the other half of the picture.
How do you monitor your WordPress site's uptime?
Use an outside service that checks your site on a schedule and alerts you when it stops responding.
Jetpack's monitor is the simplest start for WordPress sites. It is a free feature that needs only the Jetpack plugin and a working Jetpack connection, and its support page notes that it shows your site's uptime for the last 40 days, day by day, on the Protect page (Monitor your site's uptime and downtime).
Checks run every five minutes, and alerts go by email.
UptimeRobot is a common standalone option. Its free plan covers 50 monitors with five-minute checks, while paid plans check every 60 seconds on Solo, every 30 seconds on Team, and every 15 seconds on Scale, according to UptimeRobot's own pricing page (Plans and Pricing).
Shorter intervals catch brief outages faster, but for most small sites five minutes is enough to learn that something broke.
Whichever tool you pick, monitor from outside your host. A check that runs on the same server as your site cannot tell you the server is down, because it goes down with it.
What causes downtime on WordPress sites?
The most common causes are server errors, expired domains or certificates, plugin conflicts, and hosting limits.
A 500 error means the server failed to run your site's code, often after a bad plugin update. Our guide to fixing a 500 internal server error walks through the checks in order.
A 502 error usually means a gateway in front of your site could not get an answer from the server. See our guide to fixing a 502 bad gateway for that case.
A 503 error means the server is temporarily unable to handle the request, often because it is overloaded or in maintenance. Our guide to fixing a 503 service unavailable covers it.
Other causes are simpler and easier to miss. A domain that expires, an SSL certificate that lapses, or a hosting plan that runs out of disk space will all take a site offline. Traffic spikes can do the same on a small shared plan, when the server runs out of PHP workers or memory.
Keeping WordPress, plugins, and PHP current, and picking a host with headroom, prevents most of these, as covered in our guide to how to choose WordPress hosting.
What mistakes should you avoid?
The most common mistakes are trusting the advertised percentage, monitoring from inside the host, and having no alert at all.
Do not compare hosts by the uptime number alone. Two hosts can both advertise 99.9% while offering very different protection, because their exclusions, measurement methods, and remedies differ. Read the SLA text, check what counts as downtime, and find out how credits are claimed.
Do not rely on noticing downtime yourself. Most outages are found by visitors first, and every hour without an alert is an hour of lost traffic.
Set up a free monitor, even a five-minute one, and make sure its emails reach an inbox you actually read. A monitor that nobody watches is the same as no monitor at all.
Frequently asked questions
What is a good uptime percentage for a small website?
For most small business sites, 99.9% is the realistic target: about 43 minutes of allowed downtime a month. Each extra nine divides the allowance by ten, so 99.99% allows only about 4 minutes a month and costs far more to deliver. Chasing five nines is rarely worth it outside critical systems.
Does 99.9% uptime mean my site is never down for more than 43 minutes?
It depends on how it is measured. Most hosting agreements exclude scheduled maintenance and events outside the host's control, and many define availability as any successful response, not a fast one. Read the SLA exclusions before comparing two hosts by their headline number.
Can I get money back if my host misses its uptime promise?
Yes, if you pay for hosting, check the SLA for a service credit clause. When the host misses the promised uptime, the usual remedy is a credit worth a percentage of that month's fee, applied to a future invoice. Credits are small next to real losses, so treat them as a token, not compensation.
Do I need a paid uptime monitor for a small site?
A free monitor such as Jetpack's downtime monitor or UptimeRobot's free plan, which checks every five minutes, is enough for most small sites. Shorter intervals catch brief outages faster, but they cost money. What matters most is that the check runs from outside your host and that alerts reach an inbox you read.
Does downtime hurt my website?
Yes, it matters a lot. A site that returns errors or fails to load is down, whatever the cause. The usual causes are server errors, expired domains or SSL certificates, plugin conflicts, and hosting limits. Each has a different fix, so check the error code first, then the host status page.
Sources
- Service Level Objectives Google Site Reliability Engineering
- Monitor your site's uptime and downtime Jetpack
- Plans and Pricing UptimeRobot
- SLA and uptime calculator: how much downtime is 99.9%? 12happy
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


