Website uptime is the percentage of time a website is accessible and functioning correctly. It is one of the most important metrics for any online business — directly affecting user experience, revenue, and search engine rankings. This guide explains uptime in depth, from how it is calculated to what monitoring actually does.
Uptime is expressed as a percentage of total time during which a website was operational. The formula is straightforward:
Uptime % = (Total Time − Downtime) ÷ Total Time × 100
For example, if a website was down for 4 hours in a 30-day month (720 hours total), the uptime is:
(720 − 4) ÷ 720 × 100 = 99.44%
Uptime is typically measured over a rolling 30-day period, a calendar month, or a full year depending on the context. SLA guarantees are usually stated on a monthly basis.
The following table shows how much downtime each uptime percentage actually allows. The difference between 99% and 99.9% is significant in practice:
| Uptime | Downtime per day | Downtime per month | Downtime per year |
|---|---|---|---|
| 99% | 14.4 min | 7.3 hours | 3.65 days |
| 99.5% | 7.2 min | 3.65 hours | 1.83 days |
| 99.9% | 1.44 min | 43.8 min | 8.77 hours |
| 99.95% | 43.2 sec | 21.9 min | 4.38 hours |
| 99.99% | 8.6 sec | 4.38 min | 52.6 min |
| 99.999% | 0.86 sec | 26.3 sec | 5.26 min |
The 99.9% row is highlighted as the industry standard baseline for commercial websites.
Downtime is not limited to a server being completely unreachable. A website is considered "down" whenever it fails to serve its intended function to users. This includes:
Complete outage
Server is unreachable — connection refused or timed out
HTTP error responses
5xx errors (500, 502, 503, 504) indicating server-side failure
Incorrect content
Server responds 200 OK but serves an error page or blank content
Performance degradation
Response time exceeds acceptable threshold (e.g. > 5 seconds)
Partial outage
Key functionality broken (checkout, login, API) while homepage loads
SSL certificate failure
Certificate expired or invalid, blocking all HTTPS connections
Downtime has direct and indirect costs that extend well beyond the duration of the outage itself. Understanding these costs is essential for justifying investment in monitoring and redundancy:
| Cost category | Examples |
|---|---|
| Lost revenue | Abandoned purchases, missed leads, cancelled subscriptions |
| Recovery costs | Engineer time to diagnose and fix, emergency vendor support |
| Reputational damage | Negative reviews, social media complaints, reduced customer trust |
| SEO impact | Search engines reduce crawl frequency, pages may be de-indexed |
| SLA penalties | Service credits or refunds owed to customers under SLA agreements |
Uptime monitoring services work by sending automated requests to your website at regular intervals from external servers. If the request fails or the response indicates an error, the monitoring service records downtime and sends an alert.
A typical monitoring check follows this sequence:
Not all uptime monitoring services are equal. When evaluating options, consider these key capabilities:
Check frequency
1-minute checks detect outages faster than 5-minute checks. For revenue-critical sites, every minute matters.
Multiple check locations
Checks from multiple global locations eliminate false positives and detect regional outages.
Alert channels
Email, SMS, Slack, and webhook support ensures the right person is notified through their preferred channel.
SSL monitoring
Alerts before SSL certificates expire, preventing the ERR_CERT_AUTHORITY_INVALID error from reaching users.
Response time tracking
Trending response times help identify performance degradation before it becomes an outage.
Status pages
Public status pages keep users informed during incidents, reducing support ticket volume.
Alive24x7 monitors your website every minute from multiple global locations. Get instant alerts via email, SMS, or Slack the moment your site goes down — and detailed uptime reports to track your SLA compliance.