Website Uptime SLAs Explained

A hosting provider's Service Level Agreement (SLA) is a contract that specifies how available they guarantee your website will be. Most providers advertise "99.9% uptime" or similar claims. What does this actually mean? How is it measured? What happens if they fail to deliver? And more importantly, should you care?

What Uptime Means

Uptime is the percentage of time your website is accessible and working. If your site is up for 99.9% of a month, it was down for approximately 43 minutes total.

Downtime includes any period when visitors can't access your site—whether due to server failure, network issues, software bugs, or maintenance.

Uptime is typically measured as the percentage of successfully completed requests. If 99.9% of requests succeed and 0.1% fail (return an error or timeout), your uptime is 99.9%.

Common SLA Guarantees

99% means about 7 hours of downtime per month. This is basic hosting and rarely guaranteed by anyone serious.

99.5% means about 3.5 hours of downtime per month. Still relatively high and often used by budget providers.

99.9% (three nines) means about 43 minutes of downtime per month. This is the most common claim and a reasonable baseline for business websites.

99.95% means about 22 minutes of downtime per month.

99.99% (four nines) means about 4 minutes of downtime per month. This requires dedicated infrastructure and carries a higher price tag.

99.999% (five nines) means about 26 seconds of downtime per month. This is rarely guaranteed for public internet services and typically requires extreme redundancy.

How SLAs Are Measured

Monitoring points: A provider monitors your site from specific locations (usually multiple data centers) to check whether it's up. The specific frequency and method matter.

What counts as "up": Does the site need to respond quickly, or is any response enough? A site that responds in 30 seconds might technically be "up" but useless to visitors. The SLA should define acceptable response time.

Regional vs global: Some providers measure from a single location (giving an overly optimistic picture if that location is nearby). Others measure globally, which is more realistic.

Excluded downtime: Almost every SLA excludes certain types of downtime, and these exclusions are crucial.

What SLAs Usually Exclude

Scheduled maintenance: If the provider takes your site down for planned maintenance, this often doesn't count against the SLA. A provider might exclude 4 hours per month of maintenance, which is significant.

DDoS attacks: Many providers exclude downtime caused by distributed denial-of-service attacks (where an attacker floods your site with requests).

Client-side issues: If your code crashes or your database runs out of space, that's not the provider's fault. Downtime caused by your application doesn't count against the SLA.

Network issues beyond the provider's control: If your internet connection goes down at your office, that doesn't count. Neither does an issue with a third-party network.

Your own actions: If you accidentally delete your website or misconfigure something, that doesn't count against the SLA.

Force majeure: Natural disasters, wars, and other uncontrollable events are typically excluded.

These exclusions are why the headline percentage is less important than understanding what's actually guaranteed.

SLA Credits

If a provider fails to meet the SLA, they typically offer credits toward your next month's bill. This is the remedy for breach.

A 99.9% SLA might offer:

• 99.0-99.9% uptime: 10% of the month's fee
• 99.0-95% uptime: 25% of the month's fee
• Below 95%: 50% of the month's fee

This means if your site is down for a full hour (dropping to 99.86% uptime), you get 10% credit. The credit doesn't come close to the actual business impact of an hour of downtime.

Credits are often automatically applied and don't require you to ask, but check whether you need to open a support ticket.

Why SLA Percentages Are Misleading

An SLA isn't a guarantee of profitability or usability. An hour of downtime during your busiest time of day is worse than an hour at 2 AM, but the SLA treats them the same.

A provider that experiences downtime from 1 AM to 2 AM might maintain 99.9%, but if your site goes down during a product launch, customers are lost. The percentage-based SLA doesn't capture this.

Providers meeting their SLA doesn't mean your experience is good. A provider keeping uptime at 99.9% might be delaying improvements or cutting corners elsewhere.

What Actually Matters

Redundancy: Does the provider have multiple data centers? If one fails, can they automatically shift traffic to another? This is more important than the headline SLA percentage.

Monitoring: How quickly do they detect problems and respond? A provider monitoring every second can respond in minutes; one checking every hour responds slowly.

Response time: An SLA that guarantees uptime but not speed is worthless if your site responds slowly. Check the SLA for response time guarantees.

Maintenance windows: What's their policy on scheduled maintenance? A provider that takes your site down for maintenance every Sunday is worse than one that schedules it carefully.

Communication: When there's an outage, does the provider communicate clearly about cause and ETA? This matters for customer confidence.

Historical uptime: Look at the provider's actual track record. Have they met their SLA? What were the causes of downtime?

Comparing Providers

Don't choose based on SLA percentage alone. Compare:

Infrastructure: Where are data centers? Are they geographically diverse?

Actual track record: Check whether they've ever failed to meet the SLA. Look for reviews or reports from other customers.

What the SLA actually covers: Read the exclusions carefully. A 99.99% SLA that excludes DDoS, maintenance, and software issues is less meaningful than it sounds.

Support quality: When something goes wrong, can you reach support quickly? Will they help troubleshoot or just point to the SLA?

Price: Higher-SLA providers charge more. The question is whether the benefit justifies the cost for your business.

Scalability: Can the provider handle traffic spikes? Some sites fail during unexpected spikes in traffic, which might count as downtime.

FAQ

What's a realistic SLA target for a small business? 99.9% is reasonable and widely available. Five to ten nines is overkill unless you're a financial institution or similar. Once you get above 99.95%, the incremental benefit rarely justifies the cost increase.

If the provider's SLA doesn't cover DDoS, how do I handle it? Use a DDoS mitigation service like Cloudflare or Akamai. These sit in front of your site and filter malicious traffic. They're an additional cost but necessary if DDoS is a realistic threat to your business.

Can I negotiate an SLA with my provider? For larger accounts or longer contracts, sometimes yes. For small accounts, you typically get whatever SLA the provider publishes.

How do I know if my downtime counts against the SLA? When there's downtime, ask the provider. They'll investigate and tell you whether it counts. If you dispute it, escalate.

Is a private server more reliable than shared hosting? Sometimes, but not always. A poorly managed private server can be less reliable than shared hosting with redundancy. Redundancy and monitoring matter more than whether the server is private.

Should I aim for 100% uptime? No. Nothing achieves 100% uptime. Even cloud providers with exceptional redundancy have occasional issues. Targeting 99.9% or 99.95% is realistic.

Summary

An SLA is a commitment about availability, but the percentage is less important than understanding what's actually guaranteed, what's excluded, and whether the provider has the infrastructure to back it up. A 99.9% SLA from a well-managed, geographically redundant provider is more valuable than a 99.99% SLA with broad exclusions and poor monitoring. Focus on whether the provider has multiple data centers, responds quickly to problems, and has a track record of meeting their commitments. Compare providers based on infrastructure and track record, not just headline SLA percentage.