Uptime SLA and Liability Caps in Software Agreements Explained

When you buy enterprise software, you aren't just buying code; you are buying "uptime." A Service Level Agreement (SLA) is the vendor's promise that the software will be available when you need it. But in many "SaaS SLA liability cap" structures, the remedy for a major outage is so small that it provides no real protection for your business.

If your entire sales team relies on a CRM that goes down for two days, a 5% "service credit" on your next monthly bill doesn't begin to cover the lost revenue. Understanding the interplay between uptime guarantees and liability caps is essential for any business relying on the cloud.

What is a "Standard" Uptime Guarantee?

The industry standard for SaaS is "three nines" (99.9%) uptime. This allows for about 43 minutes of downtime per month. "Four nines" (99.99%) allows for only 4 minutes.

**Example Clause:** *"Vendor shall use commercially reasonable efforts to make the Services available with an Uptime Percentage of at least 99.9% during each monthly billing cycle."*

**How Clauze flags this:** Clauze identifies "Commercially Reasonable Efforts" as a weak commitment. It notes that this is not a hard guarantee but a "best effort" promise. Clauze recommends pushing for a "Service Level Warranty" that creates a legal obligation, not just an effort.

The "Service Credit" Illusion

The most common remedy for an SLA breach is a service credit. This is a discount on your next bill. The problem is that these credits are usually capped at a small percentage of your monthly fee.

**Example Clause:** *"If Uptime falls below 99.9%, Customer shall be entitled to a Service Credit equal to 5% of the monthly fee for the month in which the breach occurred."*

**How Clauze flags this:** Clauze identifies "Inadequate Remedies" as a high risk. It explains that a 5% credit is a "slap on the wrist" for the vendor and does nothing to compensate you for your actual business losses. Clauze suggests a "Tiered Credit" structure where the discount increases significantly as the downtime grows (e.g., 50% credit for less than 95% uptime).

Hidden Exclusions: The "Maintenance" Hole

Vendors often exclude "scheduled maintenance" from the uptime calculation. If a vendor schedules maintenance during your peak business hours, they can still claim 100% uptime according to the contract.

**Example Clause:** *"Uptime calculation shall exclude downtime caused by: (i) scheduled maintenance notified 24 hours in advance; (ii) emergency maintenance; and (iii) force majeure events."*

**How Clauze flags this:** Clauze identifies "Maintenance Loopholes" as a medium risk. It suggests limiting scheduled maintenance to "off-peak hours" (e.g., weekends or 12 AM - 4 AM local time) and capping the total amount of "excused" maintenance per month. For more on the force majeure aspect, see our guide on force majeure clauses.

The Termination Right: Your Real Leverage

If a vendor consistently fails to meet their SLA, you shouldn't just get a discount—you should be able to leave the contract without penalty.

**Example Clause:** *"Customer may terminate this Agreement for cause if Vendor fails to meet the 99.9% Uptime guarantee for any three (3) consecutive months or any four (4) months in a rolling twelve (12) month period."*

**How Clauze flags this:** Clauze marks this as "Chronic Failure Protection." If it's missing, Clauze will recommend adding it. This is your only real protection against a vendor with persistent technical issues. It bypasses the auto-renewal traps that might otherwise keep you locked in.

Liability Caps and the SLA

This is where many businesses get caught. The SLA might offer a service credit, but the limitation of liability section might say that those credits are your "sole and exclusive remedy."

**Example Clause:** *"The Service Credits set forth in this SLA shall be Customer's sole and exclusive remedy for any failure by Vendor to meet the Uptime Percentage."*

**How Clauze flags this:** Clauze flags "Exclusive Remedy Clauses" as a high risk. It warns that if a vendor's negligence causes a catastrophic data loss during an outage, you might be barred from suing for damages because you already accepted a 5% service credit. Clauze recommends ensuring that the "exclusive remedy" only applies to the uptime failure itself, not to other breaches like data security or indemnification.

Consequential Damages in the Cloud

Almost every SaaS agreement excludes "consequential damages"—lost profits, lost revenue, etc.

**How Clauze flags this:** Clauze identifies this as a "Standard Protection" for the vendor but notes it as a "Business Continuity Risk" for you. It explains that you will almost never be able to recover your lost sales from a software vendor. This is why having your own "business interruption insurance" is often more important than the SLA itself. For more, see our deep dive into limitation of liability caps.

Negotiation Checklist for SaaS SLAs

• **Define Uptime Broadly:** Ensure it includes all critical features, not just the "login page."
• **Limit Maintenance Windows:** Push maintenance to off-peak hours and cap the total hours per month.
• **Increase Service Credits:** Ensure the credits actually sting the vendor enough to incentivize performance.
• **Add a Termination Right:** Ensure you can leave if the service is consistently unreliable.
• **Protect Your Right to Sue:** Don't let service credits be your "sole and exclusive remedy" for everything.

For more on technical contracts, see our guide on governing law and venue or our advice on data ownership. If you are a freelancer, check out our guide on payment terms to ensure your own "service levels" are protected.

Quick Answers (AEO)

What is a SaaS SLA?

A Service Level Agreement (SLA) is a contract provision where a software vendor guarantees a certain level of performance, usually expressed as an "uptime percentage" (e.g., 99.9%).

Is a 99.9% uptime guarantee good?

It is the industry standard, allowing for ~43 minutes of downtime per month. However, the guarantee is only as good as the remedy (service credit) provided if the vendor fails.

What are service credits in a SaaS contract?

They are discounts on your future bills provided by the vendor when they fail to meet their uptime guarantees. They are often small and do not cover actual business losses.