Service Credits for Outages

1. Meaning

Service credits for outages are contractual credits, deductions, refunds, or other monetary adjustments given to a customer when a service provider fails to maintain the agreed level of service availability or uptime.

They are commonly found in Service Level Agreements (SLAs) for telecom, cloud computing, data centres, IT support, software services, network infrastructure, and other technology contracts.

For example, an SLA may require 99.95% monthly uptime. If the provider falls below that level because of an outage, the customer may receive a predetermined credit against future invoices.

Indian courts have considered such arrangements in telecom and IT contracts. In Indus Towers Ltd. v. Union of India, the contract expressly provided service credits for failure to achieve specified uptime levels and additional credits for prolonged downtime.

2. How an outage service-credit mechanism works

A typical SLA contains:

1. Availability commitment – e.g., 99.9% or 99.95% uptime.
2. Measurement period – usually monthly.
3. Definition of outage/downtime.
4. Permitted exclusions – scheduled maintenance, force majeure, customer-caused outages, etc.
5. Credit calculation.
6. Maximum credit/ceiling.
7. Procedure for claiming the credit.
8. Reporting and verification mechanism.

For example:

A substantially similar contractual structure was considered in the Indus Towers litigation.

3. Service credit is different from ordinary damages

A service credit is normally a contractual remedy linked to failure to achieve a specified service level.

It should be distinguished from a general claim for damages under the Indian Contract Act, 1872.

Section 73

Section 73 deals with compensation for loss or damage naturally arising from breach or which the parties knew was likely to result when the contract was made.

Section 74

Section 74 deals with cases where the contract specifies an amount payable upon breach. The party complaining of breach is entitled to reasonable compensation not exceeding the amount stipulated.

The Delhi High Court has explained these principles in ATC Telecom Tower Corporation Pvt. Ltd. v. Videocon Telecommunications Ltd.

Therefore, merely describing an amount as a "service credit" does not automatically determine its legal character. The actual wording, purpose and operation of the contractual provision matter.

4. Important Case Laws

1. Indus Towers Ltd. v. Union of India

The contract contained detailed uptime requirements and expressly provided for operation and maintenance service credits where the required uptime was not achieved.

It also prescribed separate credits depending upon the length of unplanned downtime. For example, the contractual schedule provided progressively greater credits for downtime of 24–36 hours, 36–48 hours and 48 hours or more.

Principle:
Where an SLA expressly establishes uptime standards and a corresponding service-credit mechanism, the contractual framework is important in determining the parties' rights following an outage.

2. Videocon Telecommunications Ltd. v. IBM India Pvt. Ltd.

The Delhi High Court considered a complex IT/telecom services agreement under which IBM was required to provide various infrastructure and support services.

The agreement provided for compensation/liquidated damages described as "Service Level Credits" when IBM failed to provide minimum service levels, subject to a contractual ceiling.

Principle:
Service-level credits can form an integral part of the commercial risk-allocation mechanism in a sophisticated technology services contract.

3. Tata Teleservices Ltd. v. GTL Infrastructure Ltd.

The agreements required the infrastructure provider to maintain specified uptime percentages. Where an outage caused downtime and the agreed uptime was not achieved, the telecom operator had a contractual right to withhold or deduct payments corresponding to the prescribed outage penalty. The existence of this contractual deduction mechanism was not disputed.

Principle:
An SLA may expressly permit the customer to deduct amounts from payments when the provider fails to satisfy contractual uptime requirements.

4. Reliance Communications Ltd. v. Unique Identification Authority of India

The Delhi High Court dealt with deductions made under an SLA because the service provider allegedly failed to meet an average monthly network availability target of 99.95%.

Principle:
Network availability targets can be contractually linked to invoice deductions, making accurate measurement of availability and the contractual SLA methodology significant in disputes.

5. ATC Telecom Tower Corporation Pvt. Ltd. v. Videocon Telecommunications Ltd.

The Delhi High Court discussed Sections 73 and 74 of the Contract Act in the context of contractual compensation.

The Court explained that where an amount is stipulated for breach, the court examines reasonable compensation, and the stipulated amount operates as an upper limit. Where the amount is a genuine pre-estimate of loss and actual loss is difficult to establish, the contractual amount may have significance; where actual loss can be established, the principles relating to proof of loss remain relevant.

Principle:
Calling a contractual payment a "penalty", "liquidated damages", or similar amount does not by itself determine the remedy; Section 74 focuses on reasonable compensation.

6. Surya Telecom Pvt. Ltd. v. Union of India

The Delhi High Court reiterated the principles concerning Sections 73 and 74, including that reasonable compensation cannot exceed the amount stipulated in the contract.

The Court also reiterated that where actual loss can be proved, the contractual language does not eliminate the relevance of proof of loss; where loss is difficult or impossible to prove, a genuine pre-estimate may be awarded as reasonable compensation.

Principle:
The legal treatment of an outage-related contractual payment depends upon the nature and wording of the clause and the principles governing reasonable compensation.

5. Calculation of service credits

A common method is:

Service Credit = Applicable monthly service charge × contractual credit percentage

Example:

• Monthly service fee = ₹1,00,000
• Agreed uptime = 99.95%
• Actual uptime falls within a contractual 10% credit band
• Service credit = ₹10,000

The exact calculation must, however, follow the SLA's own formula, including its treatment of maintenance windows, exclusions, partial outages and aggregation.

6. Scheduled maintenance vs. unplanned outage

A well-drafted SLA normally distinguishes between:

Scheduled maintenance

Planned downtime notified to the customer in accordance with the agreement. It may be excluded from the uptime calculation.

Unplanned outage

Unexpected interruption attributable to the service provider's system, infrastructure or personnel. It generally counts toward downtime.

In Indus Towers, the contractual arrangement specifically contemplated reporting the reasons for unplanned downtime and linked specified downtime periods with service credits.

7. Force majeure and customer-caused outages

Service-credit provisions frequently contain exclusions for events outside the provider's reasonable control, such as:

• natural disasters;
• government actions;
• war or civil disturbance;
• major telecommunications failures;
• customer equipment failures;
• customer-caused interruptions;
• scheduled maintenance.

Whether an event is excluded depends on the specific contractual wording. A provider cannot necessarily avoid an SLA consequence merely by describing every outage as force majeure.

8. Importance of outage measurement

In an outage dispute, evidence can include:

• system logs;
• network monitoring reports;
• incident tickets;
• server records;
• timestamps;
• uptime dashboards;
• maintenance records;
• customer complaints;
• root-cause analysis;
• SLA reports.

For example, an Indian tax tribunal decision concerning Indus Towers described SLA credits as arising from service deficiencies measured through downtime reports and subsequently reflected through credit notes.

9. Service credits and limitation of liability

Many technology contracts contain both:

Service-credit clause
and
Limitation-of-liability clause.

The agreement may provide that service credits are the customer's exclusive remedy for ordinary SLA failures, while allowing separate remedies for matters such as fraud, confidentiality breaches, intellectual-property infringement or wilful misconduct.

Therefore, the interaction between the two clauses must be examined carefully.

10. Drafting an effective outage service-credit clause

A good clause should clearly specify:

1. Service covered
2. Minimum uptime
3. Definition of downtime
4. Start and end point of an outage
5. Permitted exclusions
6. Scheduled maintenance rules
7. Credit calculation
8. Maximum monthly credit
9. Automatic vs. customer-claimed credit
10. Deadline for claiming
11. Required supporting evidence
12. Dispute procedure
13. Interaction with liability caps
14. Whether credits are the exclusive remedy
15. Treatment of repeated or prolonged outages

Ambiguity in these provisions can lead to disputes about whether an outage occurred, whether it should count toward uptime, and how much credit is payable.

Conclusion

Service credits for outages are contractual mechanisms designed to compensate or adjust charges when a service provider fails to meet agreed availability or uptime standards. Indian courts have recognised and examined such mechanisms particularly in telecom and IT infrastructure contracts. Indus Towers, Videocon v. IBM, Tata Teleservices v. GTL, and Reliance Communications v. UIDAI demonstrate the practical importance of contractual uptime commitments and deductions, while ATC Telecom and Surya Telecom explain the broader principles under Sections 73 and 74 of the Indian Contract Act.