What is a Service Level Agreement (SLA) addendum?
Are SLA service credits enforceable in South Africa?
“A penalty (which includes an agreed service credit) is valid and enforceable, but if a court is satisfied that it is out of proportion to the prejudice suffered by the creditor by reason of the breach, the court may reduce the penalty to such extent as it considers equitable in the circumstances.”
“When a supplier undertakes to perform a service, the consumer has a right to its timely performance and completion, to timely notice of any unavoidable delay, and to performance in a manner and of a quality that persons are generally entitled to expect — a statutory baseline that sits behind an SLA where the customer is a consumer under the Act.”
When you need a Service Level Agreement Addendum
- When a cloud, SaaS, hosting, or managed-service provider commits to an uptime or availability guarantee and the customer wants a measurable, enforceable promise rather than a vague best-efforts statement.
- When the customer’s own business depends on the service being available — for example a payment, booking, or trading platform — and outages cause real, quantifiable harm that justifies a service-credit remedy.
- When the provider needs to ring-fence its exposure by defining exactly what counts as downtime, excluding scheduled maintenance and third-party failures, and capping financial consequences at agreed service credits.
- When a master cloud services agreement is signed and the commercial service-level terms need to live in a separate, easily-updated schedule rather than the body of the contract.
- When the customer is a consumer (or small business below the CPA threshold) and the parties want the SLA to align with, rather than fall short of, the section 54 quality-of-service baseline.
What a Service Level Agreement Addendum should contain
Availability (uptime) target and measurement window
State the committed availability as a precise percentage — e.g. 99.5% or 99.9% — and the window over which it is measured (usually a calendar month). Define the exact formula: how total minutes, downtime minutes, and excluded minutes are counted. An unmeasurable target (“high availability”, “best efforts”) gives the customer nothing to enforce and the provider nothing to manage against.
Definition of downtime and exclusions
Define what counts as downtime — typically the service being unavailable or materially degraded — and, critically, the exclusions: scheduled maintenance within agreed windows, customer-caused outages (the customer’s environment, configuration, or misuse), force majeure events, and failures in third-party networks or upstream providers outside the provider’s control. The exclusions are where most SLA disputes are won or lost, so draft them tightly.
Service credits as the remedy
Set out the service-credit schedule: the rebate (as a percentage of the monthly fee) payable at each band of missed availability, scaled to severity. State clearly whether credits are the sole and exclusive financial remedy for a service-level breach. Credits are a penalty under the Conventional Penalties Act, so keep them proportionate to the customer’s likely prejudice to maximise the chance a court enforces them as drafted.
Maintenance windows and change notice
Fix when the provider may take the service down for planned maintenance — usually defined low-traffic windows — and the advance notice required for scheduled and emergency maintenance. Maintenance performed inside an agreed window is normally excluded from downtime, so the boundary between “scheduled maintenance” (excluded) and “unplanned outage” (counts against the SLA) must be unambiguous.
Chronic / persistent-failure termination right
Give the customer a right to terminate (often without penalty, and sometimes with a refund) where the provider misses the availability target in several consecutive or rolling months, or suffers a single catastrophic outage beyond a defined threshold. This is the customer’s ultimate protection where service credits alone do not cure a structurally failing service.
Measurement, monitoring and reporting
Specify how availability is measured — provider monitoring, third-party tooling, or an agreed methodology — who bears the onus of proof in a dispute, and the cadence of availability reporting. Tie the credit-claim process to this: how and by when the customer must claim a credit, and how a disputed measurement is resolved. Without an agreed measurement method, the headline percentage is unenforceable in practice.
Severity / priority tiers (where degraded service is covered)
Where the SLA covers more than binary up/down — e.g. performance, latency, or partial degradation — define the severity tiers and the service level attaching to each. This keeps the SLA aligned with the support addendum’s severity model and avoids the two documents using inconsistent definitions of a “critical” failure.
Interaction with the support addendum and master agreement
State expressly that this SLA governs availability and the support addendum governs response and resolution of faults, and that the limitation-of-liability, exclusion, and force-majeure provisions of the master agreement apply. Clarify that service credits sit within (not on top of) the overall liability cap unless the parties intend otherwise.
SLA addendum vs support addendum vs master cloud services agreement
| Feature | SLA addendum | Support addendum | Cloud services agreement |
|---|---|---|---|
| Governs | Availability / uptime of the service | Response and resolution of faults and queries | The whole commercial and legal relationship |
| Core metric | Uptime % over a measurement window | Response (and sometimes resolution) times by severity | Scope, fees, term, IP, liability, data |
| Typical remedy | Service credits (often sole financial remedy) | Escalation; sometimes credits for missed response | Damages, termination, indemnities (subject to caps) |
| SA touchpoint | Conventional Penalties Act (credits as penalty); CPA s 54 | Conventional Penalties Act where backed by credits; CPA s 54 | Common law of contract; CPA; POPIA; ECTA |
| Lives where | Schedule to the master agreement | Schedule to the master agreement | The master contract itself |
Common South African pitfalls
- An unmeasurable target: an SLA that promises “high availability” or “best efforts” without a defined percentage, measurement window, and counting formula gives the customer nothing to enforce. The headline number is worthless unless the SLA also says exactly how it is measured and who proves the breach.
- Disproportionate or punitive credits: service credits are a penalty under the Conventional Penalties Act, and a court may reduce a credit that is out of proportion to the customer’s actual prejudice. Credits set as a punishment rather than a genuine, scaled remedy risk being read down — undermining the certainty the SLA was meant to give.
- Silence on whether credits are the sole remedy: if the SLA does not say whether service credits are the exclusive financial remedy, the parties are left to argue whether the customer can also claim damages for the same breach. The Conventional Penalties Act prevents recovering both penalty and damages unless the contract reserves it — so state the position expressly.
- Loose or missing exclusions: failing to exclude scheduled maintenance, customer-caused outages, force majeure, and third-party network failures exposes the provider to credit claims for events outside its control. Conversely, exclusions drafted so widely that almost any outage is excluded make the uptime guarantee illusory and invite a CPA challenge.
- Contracting out of the CPA where it applies: where the customer is a consumer under the Consumer Protection Act, the section 54 right to a quality service cannot be excluded. An SLA that purports to limit the provider’s obligations below that statutory baseline is, to that extent, unenforceable against a consumer.
Frequently asked questions
Are SLA service credits legally enforceable in South Africa?
Yes. Service credits are a penalty stipulation, and penalty and pre-estimated-damages clauses are valid and enforceable under the Conventional Penalties Act 15 of 1962. A court will enforce a service credit as drafted, but section 3 allows it to reduce a credit that is out of proportion to the prejudice the customer actually suffered.
What uptime percentage should an SLA commit to?
There is no legally fixed figure — it is a commercial choice. Common targets are 99.5%, 99.9%, or higher, each expressed as a percentage of a defined measurement window (usually a calendar month). What matters legally is that the target is precise, the measurement method is agreed, and the credit regime tied to it is proportionate.
What is the difference between an SLA and a support addendum?
An SLA governs availability — whether the service is up and meeting its uptime target. A support addendum governs how quickly the provider responds to and resolves faults and queries, usually with response (and sometimes resolution) times per severity level. They are complementary schedules and should use consistent severity definitions, but they measure and remedy different things.
Can a court reduce or strike out a service credit?
A court will not strike a service credit out merely because it is a penalty — penalties are valid in South Africa. But under section 3 of the Conventional Penalties Act it may reduce a credit to the extent it is out of proportion to the prejudice the customer suffered. The party seeking the reduction must show the disproportion, and the court weighs prejudice broadly.
Should service credits be the only remedy for downtime?
That is a deliberate drafting choice, and it should be stated expressly. Many SLAs make credits the sole financial remedy for a service-level breach, capping the provider’s exposure. The Conventional Penalties Act prevents a customer recovering both the credit and damages for the same breach unless the contract reserves that right — so silence creates uncertainty.
What does the SLA exclude from downtime?
Standard exclusions are scheduled maintenance within agreed windows, outages caused by the customer’s own environment or misuse, force majeure events, and failures in third-party networks or upstream providers outside the provider’s control. These exclusions define the real scope of the uptime guarantee and are where most SLA disputes are decided.
Does the Consumer Protection Act apply to a cloud SLA?
It can. Where the customer is a consumer (including a small business below the CPA threshold), section 54 of the Consumer Protection Act gives a right to a service of the quality persons are generally entitled to expect, and that right cannot be excluded. An SLA can build on that baseline but cannot lawfully drop the provider’s obligations below it.
When can a customer terminate for poor service?
When the SLA gives a chronic-failure termination right — typically where the provider misses the availability target in several consecutive or rolling months, or suffers a single catastrophic outage beyond a defined threshold. This is the customer’s ultimate remedy where service credits alone do not cure a structurally failing service, and it is worth negotiating explicitly.
Sources & authority
This guide is general information, not legal advice. It reflects the law as at June 2026.