Uptime and SLA — what the numbers really mean

What is Uptime and Why Can Its Numbers Be Misleading?

When a web hosting company claims to guarantee uptime of 99.9%, many users assume their service will be available almost all the time. But the reality is that this 0.1% downtime can have a significant impact on your business. In this article, instead of repeating promotional numbers, we will precisely calculate how many minutes of downtime each level of uptime permits per month, year, or even decade. We will also examine what an SLA (Service Level Agreement) typically does not cover and why you should not rely solely on percentages.

Precise Calculation of Permissible Downtime Minutes at Each Uptime Level

To better understand, let's start with a simple formula. If a service is available over a specific period (e.g., a 30-day month), the permissible downtime is calculated as follows:

Permissible Downtime = (1 - (Uptime Percentage / 100)) × Total Minutes in the Period

For example, in a 30-day month (43,200 minutes):

• 99% Uptime: (1 - 0.99) × 43200 = 432 minutes (about 7.2 hours of downtime)
• 99.9% Uptime: (1 - 0.999) × 43200 = 43.2 minutes
• 99.99% Uptime: (1 - 0.9999) × 43200 = 4.32 minutes
• 99.999% Uptime: (1 - 0.99999) × 43200 = 0.432 minutes (about 26 seconds)

Now let's calculate these numbers for longer periods:

Calculation for One Year (365 days = 525,600 minutes)

• 99% Uptime: 5,256 minutes (about 3.65 days of downtime)
• 99.9% Uptime: 525.6 minutes (about 8.76 hours)
• 99.99% Uptime: 52.56 minutes (less than an hour)
• 99.999% Uptime: 5.256 minutes (about 5 minutes and 15 seconds)

Important note: Many companies calculate uptime on a monthly or yearly basis, but the SLA is usually based on a monthly or yearly average. If you have a 10-hour outage one month and no issues the next, the yearly average might still show 99.9%, but you would have suffered losses during that specific month.

Calculation for One Decade (10 years = 5,256,000 minutes)

• 99.9% Uptime: 5,256 minutes (about 3.65 days of downtime per decade)
• 99.99% Uptime: 525.6 minutes (about 8.76 hours)
• 99.999% Uptime: 52.56 minutes (less than an hour)

These numbers show that even a seemingly small percentage difference in uptime creates a huge difference over the long term. For an e-commerce website where every hour of downtime means lost revenue, the difference between 99.9% and 99.99% could amount to hundreds of millions of Tomans per year.

What Does an SLA Not Cover? Hidden Clauses in Contracts

An SLA (Service Level Agreement) is a document that specifies the guaranteed service level, but it usually has many exceptions. Below, we examine the most common items not covered by an SLA:

Scheduled Maintenance

Most hosting companies exclude outages caused by security updates, hardware repairs, or network upgrades from uptime calculations. These outages are usually announced in advance, but if they occur during your business peak hours, they can still cause losses. Be sure to check the SLA to see if these outages are included in downtime calculations.

External Network Issues

If the problem originates from your ISP, a large-scale DDoS attack, or an outage in upstream networks (e.g., a problem at an internet exchange), it is typically not covered by the SLA. For example, if your server is in the ServerNet data center but your users cannot access the site due to an issue with their ISP, this downtime is not counted in the SLA.

Customer-Caused Issues

If you change server settings yourself, run a faulty script, or exceed resource limits, any resulting downtime is not covered by the SLA. Additionally, if your application (e.g., WordPress) goes down due to a defective plugin, this downtime is your responsibility.

DDoS Attacks and Cyber Attacks

Many SLAs consider DDoS attacks as "force majeure" or events beyond control and exclude them from uptime calculations. Some companies offer basic DDoS protection, but if an attack exceeds that protection level, the downtime is not counted.

Downtime Below a Certain Threshold

Some SLAs ignore outages shorter than 5 or 10 minutes. This means if your server is down for 4 minutes, it is not included in the uptime calculation. This can be problematic for sensitive services (e.g., online banking).

How to Evaluate a Real SLA?

To evaluate an SLA, instead of focusing solely on the uptime percentage, pay attention to the following points:

Measurement Unit and Calculation Period

The SLA should specify the period over which uptime is calculated: monthly, quarterly, or yearly. The measurement unit (minutes, hours, or percentage) should also be clear. A good SLA typically reports downtime in minutes, not just percentages.

Outage Reporting and Claim Process

Check what process you need to follow to report an outage. Do you need to submit a support ticket? What is the deadline for filing a claim? Some companies only accept outages reported within the first 24 hours. Also, specify the required documentation (e.g., server logs or monitoring tool screenshots).

Penalties and Compensation (SLA Credits)

Typically, if the SLA is violated, the hosting company will give you "service credits" that can be used on your next invoice. However, these credits are usually limited. For example, if uptime is guaranteed at 99.9% but drops to 99.5%, you might receive a 5% discount on your monthly fee. This amount is usually negligible compared to the losses caused by the outage.

A Common Mistake: Relying on Uptime Without Independent Monitoring

Many users trust the uptime report provided by the hosting company. However, these reports may be taken from the company's own servers and may ignore minor outages. For example, if your server is available but your website is not working due to a load balancer or database issue, this may not be reflected in the server's uptime report.

Solution: Use a third-party monitoring service (e.g., UptimeRobot or Pingdom) that checks your website from multiple geographic locations. These tools usually provide more accurate reports of actual downtime. You can also analyze your server logs using simple scripts to detect real outages.

Conclusion: Take Uptime Seriously, But with an Open Mind

Uptime numbers, if interpreted correctly, are a useful tool for choosing a hosting service. But do not forget that:

• Every 0.1% decrease in uptime results in about 8.76 hours of downtime per year.
• SLAs usually have many exceptions that can leave a large portion of outages uncovered.
• The best way to ensure real uptime is to use third-party monitoring and carefully review the SLA.

If you are looking for a hosting service with high uptime and a transparent SLA, companies like ServerNet that offer professional cloud infrastructure can be a good option. But always read the SLA line by line before purchasing and ask support exactly what it covers. Remember: in the world of web hosting, "99.9%" alone is not enough; what matters is transparency and reliability in practice.