The SaaS Founder's Guide to Uptime SLAs and What They Really Mean

Key Facts

Direct answer: The direct answer is that an uptime SLA is a percentage that represents the maximum allowed downtime in a given period. 99.9 percent means 43 minutes of downtime per month. 99.99 percent means 4.3 minutes per month.
What Uptime Percentages Actually Mean: | SLA | Monthly Downtime | Annual Downtime |.
What SLA Should You Promise?: Promise: 99.5 percent (3.6 hours/month).
How to Measure Uptime: Uptime is measured by an external monitoring service that checks your app's URL at regular intervals.
What Happens When You Miss Your SLA: If your actual uptime falls below your SLA, you typically owe the customer a credit (e.g., "10 percent of the monthly fee for each percentage point below the SLA").

When an enterprise customer asks "What is your uptime SLA?", do you know what to say? An SLA (Service Level Agreement) is a promise about your app's availability, and it carries financial consequences if you break it. Saying "99.99 percent" without understanding what it means is a recipe for trouble. This article is the founder's guide to uptime SLAs, what they really mean, and how to set realistic expectations.

The direct answer is that an uptime SLA is a percentage that represents the maximum allowed downtime in a given period. 99.9 percent means 43 minutes of downtime per month. 99.99 percent means 4.3 minutes per month. Before promising an SLA, make sure you can actually achieve it. For more on reliability, see our article on monitoring your SaaS without hiring a DevOps engineer.

What Uptime Percentages Actually Mean

| SLA | Monthly Downtime | Annual Downtime |

|-----|-----------------|-----------------|

| 99% | 438 minutes (7.3 hours) | 87.6 hours (3.6 days) |

| 99.5% | 219 minutes (3.6 hours) | 43.8 hours (1.8 days) |

| 99.9% (three nines) | 43 minutes | 8.8 hours |

| 99.95% | 21.6 minutes | 4.4 hours |

| 99.99% (four nines) | 4.3 minutes | 52.6 minutes |

| 99.999% (five nines) | 0.4 minutes (26 seconds) | 5.3 minutes |

As you can see, each "nine" adds a zero to the requirement. Going from 99.9 percent to 99.99 percent reduces the allowed downtime from 43 minutes to 4.3 minutes per month — a 10x improvement that requires significant engineering effort.

What SLA Should You Promise?

For early-stage SaaS (1-100 customers)

Promise: 99.5 percent (3.6 hours/month). This is realistic for a single-region deployment without high availability. It gives you room for deployments, maintenance, and occasional outages.

For growth-stage SaaS (100-1000 customers)

Promise: 99.9 percent (43 minutes/month). This requires blue/green deployments (zero-downtime deploys), automated rollback, health checks, and monitoring. Deployxa provides these features automatically.

For enterprise SaaS (1000+ customers)

Promise: 99.95 percent (21.6 minutes/month). This requires everything above plus redundant infrastructure, multi-region deployment, and automated failover.

What NOT to promise

Do not promise 99.99 percent unless you have multi-region deployment with automated failover. A single-region deployment cannot achieve 99.99 percent.
Do not promise 100 percent. It is impossible. Every system has downtime.
Do not promise an SLA you cannot measure. If you do not have uptime monitoring, you do not know your actual uptime.

How to Measure Uptime

Uptime is measured by an external monitoring service that checks your app's URL at regular intervals:

Use Uptime Robot (free). Checks your app every 1-5 minutes from multiple locations. Tracks uptime percentage and sends alerts on downtime.

Point the monitor at your health check. Monitor https://myapp.com/health, not just the homepage. This ensures the monitor checks the app's health, not just whether the server responds.

Calculate uptime monthly. Uptime = (total minutes - downtime minutes) / total minutes * 100.

For more on monitoring, see our article on monitoring your SaaS without hiring a DevOps engineer.

What Happens When You Miss Your SLA

If your actual uptime falls below your SLA, you typically owe the customer a credit (e.g., "10 percent of the monthly fee for each percentage point below the SLA"). This is called an SLA credit.

How to handle SLA credits

Acknowledge the miss. Do not try to hide it. Customers can check your status page.
Calculate the credit. Apply the formula in your SLA.
Apply the credit automatically. Do not make the customer ask for it.
Communicate. Email the customer: "Our uptime in [month] was [X] percent, which is below our SLA of [Y] percent. We have applied a credit of [Z] to your account."
Prevent recurrence. Conduct a post-mortem and implement preventive measures.

For more on incident communication, see our article on the SaaS founder's guide to status pages and customer communication.

Common Pitfalls and Troubleshooting

The first pitfall is promising an SLA you cannot achieve. If you promise 99.99 percent but your actual uptime is 99.5 percent, you owe SLA credits every month. The fix is to promise a realistic SLA based on your actual uptime.

The second pitfall is not measuring uptime. If you do not measure uptime, you do not know if you are meeting your SLA, and you cannot calculate credits. The fix is to use an external monitoring service.

The third pitfall is not excluding scheduled maintenance. If you count scheduled maintenance as downtime, your uptime looks worse than it is. The fix is to exclude scheduled maintenance from the uptime calculation (but notify customers in advance).

The fourth pitfall is not having a status page. Without a status page, customers cannot verify your uptime, which erodes trust. The fix is to set up a status page.

The fifth pitfall is not handling SLA credits gracefully. If a customer has to ask for the credit, it creates friction. The fix is to apply credits automatically and communicate proactively.

Conclusion: Promise What You Can Deliver

An SLA is a promise, and breaking it has financial consequences. Promise a realistic SLA based on your actual uptime (99.5 percent for early-stage, 99.9 percent for growth-stage), measure your uptime with an external service, and handle SLA credits gracefully when you miss. Do not over-promise — it is better to promise 99.5 percent and deliver 99.9 percent than to promise 99.99 percent and deliver 99.5 percent.

Ready to set your SLA? Check your actual uptime (via Uptime Robot), set a realistic SLA, and publish it on your website. For more, see monitoring your SaaS without hiring a DevOps engineer and the SaaS founder's guide to status pages. Explore our free developer tools to speed up your workflow.