Service Level Agreement: Uptime, Credits and Remedies
What an SLA covers in India: uptime arithmetic, response times, exclusions, service credits under sections 73 and 74 of the Contract Act, and remedies.
A service level agreement (SLA) turns “reliable service” into measurable targets and fixes in advance what the customer receives when a target is missed. In India, service credits are likely to be treated as a sum named in the contract under section 74 of the Indian Contract Act, 1872, so they should be enforceable where they are a reasonable estimate of the customer’s loss.
Where the SLA sits
An SLA is usually a schedule to a master service agreement or a SaaS subscription agreement. The master agreement carries the liability cap, IP and dispute terms, a statement of work carries project scope, and the SLA carries the performance targets. The MSA and SOW guide explains that structure. Two drafting points matter: the order-of-precedence clause should say which document wins on a conflict, and the master service agreement should say whether service credits count towards the overall liability cap.
Availability: what the percentages allow
Availability is the share of the measurement period for which the service was usable: total minutes minus downtime minutes, divided by total minutes. A 30-day month has 43,200 minutes.
| Monthly uptime target | Downtime allowed (minutes) | In plain terms |
|---|---|---|
| 99.5% | 216 | 3 hours 36 minutes |
| 99.9% | 43.2 | About 43 minutes |
| 99.99% | 4.32 | About 4 minutes 19 seconds |
The number is only as good as its definitions. State what counts as downtime (a total outage only, or serious degradation too), which monitoring tool measures it, and whether the period is a calendar month or a quarter. A quarterly average hides a bad month.
Response and resolution times
Support targets are set by severity. The figures below are illustrative, not a standard.
| Severity | Example | Response | Resolution or workaround |
|---|---|---|---|
| 1 | Service down for all users | 30 minutes | 4 hours |
| 2 | Major feature unusable | 2 hours | 1 business day |
| 3 | Minor defect with a workaround | 1 business day | Next release |
Define “response” as a human acknowledgment, not an automated reply. Say whether a workaround counts as resolution, what the support hours are, and that the clock stops while the provider waits for information from the customer.
Exclusions
- Scheduled maintenance, with advance notice and a monthly cap on hours.
- Faults caused by the customer, its network or its other vendors.
- Force majeure, and internet failures outside the provider’s control.
- Suspension for non-payment, and beta or trial features.
Customers should check that an exclusion applies only to the extent the excluded event caused the failure, and that the provider’s own hosting vendor is not excluded.
Service credits and sections 73 and 74
A service credit is a percentage of the monthly fee, tiered by how far the target was missed, capped, and usually set off against the next invoice. A hypothetical example: the fee is Rs 2,00,000 a month and the target is 99.9%. Downtime in a 30-day month is 259 minutes, so availability is 99.4%. If the tier for 99.0% to 99.9% carries a 10% credit, the customer receives Rs 20,000.
Section 73 of the Contract Act gives compensation for loss that flows naturally from a breach. Section 74 applies where the contract itself names a sum payable on breach: the injured party receives reasonable compensation not exceeding that sum, whether or not actual loss is proved. The Supreme Court explained in Fateh Chand v. Balkishan Dass (1963), ONGC v. Saw Pipes (2003) and Kailash Nath Associates v. DDA (2015) that the named sum is a ceiling, that a genuine pre-estimate of loss can be awarded as it stands where loss is hard to quantify, and that some loss must have been suffered. Indian law does not enforce a penalty as such. It awards what is reasonable.
For an SLA this means modest, proportionate credits are on firm ground, because the loss from an hour of downtime is real but difficult to prove. Credits set far above any likely loss risk being cut down. Calling them a genuine pre-estimate helps but does not decide the point.
Sole remedy and termination for chronic failure
Providers want credits to be the customer’s sole and exclusive remedy for a missed service level. Such clauses are usually respected between businesses, though not for fraud or wilful default, so customers should negotiate exceptions before signing: a right to terminate for repeated failure, and no restriction on claims for data breaches, confidentiality breaches or wilful default. A chronic-failure clause might allow termination without exit fees if availability falls below target in three consecutive months, or in any four months out of twelve. Those triggers are examples.
Reporting, data and security
The SLA should require a monthly report of measured performance, a root-cause analysis for serious incidents and a time limit for claiming credits.
Data and security terms usually sit in the master agreement or a data processing schedule: security standards, backups, breach notification, and return or deletion of data on exit. Until the Digital Personal Data Protection Act, 2023 takes full effect in May 2027, section 43A of the Information Technology Act, 2000 and the 2011 rules on reasonable security practices apply. The DPDP Act lets a data fiduciary use a processor only under a valid contract and keeps the fiduciary responsible. CERT-In’s 2022 directions require specified cyber incidents to be reported within six hours, which is why customer contracts set short notification times. The DPDP checklist covers the privacy side, and the service level agreement should cross-refer to those terms.
Frequently asked questions
Sources
Written by the DraftingBase drafting desk. Law and stamp rates change; this guide reflects the position as of 11 November 2026. It is general information, not legal advice for your facts.