Cloud Computing Service Disputes

1. Meaning

Cloud Computing Service Disputes are legal disputes arising from agreements under which a cloud provider supplies services such as computing power, storage, databases, software, networking, hosting, cybersecurity, backup, or managed infrastructure through the internet.

Typical parties include:

• Cloud service provider
• Cloud reseller/distributor
• Data-centre operator
• Enterprise/customer
• Software developer
• Managed-service provider
• End user

In India, such disputes are generally governed by contract law, the Information Technology Act, 2000, the Arbitration and Conciliation Act, 1996, the Consumer Protection Act where applicable, the GST/IGST framework, data-protection law, and general principles of damages and commercial litigation.

A recent Indian example illustrates the contractual nature of these disputes: in Ingram Micro Platform Technology India Pvt. Ltd. v. Creator Economy Tech Pvt. Ltd. (2026), the dispute concerned AWS cloud infrastructure usage, unpaid invoices exceeding ₹7 crore, contractual terms, and an arbitration clause contained in the relevant sales terms. 

2. What Is a Cloud Computing Service Agreement?

A cloud agreement generally establishes:

1. Services to be supplied
2. Pricing and billing methodology
3. Service-level commitments
4. Availability/uptime
5. Data storage and security
6. Backup and disaster recovery
7. Intellectual-property rights
8. Customer responsibilities
9. Acceptable-use requirements
10. Suspension and termination rights
11. Data deletion/return
12. Confidentiality
13. Limitation of liability
14. Indemnification
15. Governing law
16. Arbitration/jurisdiction
17. Force-majeure provisions.

Cloud contracts are often standard-form or click-wrap agreements, although large enterprise customers may negotiate bespoke master service agreements.

3. Major Types of Cloud Computing Service Disputes

A. Non-payment disputes

The customer may fail to pay:

• monthly subscription charges;
• metered usage charges;
• storage charges;
• data-transfer charges;
• support charges;
• managed-service charges.

The provider may then suspend or terminate the account.

The recent Ingram Micro–Creator Economy Tech dispute is particularly relevant because the provider sought arbitration concerning unpaid AWS consumption invoices.

B. Service outage disputes

A customer may claim that the cloud provider failed to maintain promised availability.

For example:

A cloud contract promises 99.99% availability, but repeated outages cause a customer's online business to lose transactions.

The legal issues include:

• Was the SLA breached?
• Was the outage covered by an exception?
• Was there a force-majeure event?
• Were service credits the exclusive remedy?
• Can the customer recover consequential losses?

4. Service-Level Agreement (SLA) Disputes

An SLA establishes measurable standards for cloud performance.

It may address:

A major issue is whether an SLA provides merely a service credit or permits a customer to claim additional damages.

In HI Technology Corp. v. Quality Investment Properties Suwanee LLC, a data-centre agreement provided service credits for power outages while also containing limitations on consequential damages. The dispute demonstrated how contractual SLA remedies and liability limitations can substantially affect recovery after an outage.

5. Data Loss and Data Corruption

Cloud customers may allege that the provider:

• deleted data;
• corrupted databases;
• failed to maintain backups;
• failed to restore data;
• improperly migrated data;
• caused unauthorized modification;
• failed to protect against cyberattacks.

The important contractual questions are:

1. Who was responsible for backup?
2. Was the customer responsible for its own data?
3. Did the provider guarantee restoration?
4. Was the provider merely providing infrastructure?
5. What liability cap applies?
6. Is consequential loss excluded?

Cloud contracts frequently distinguish between the provider's infrastructure responsibilities and the customer's responsibility for its own applications and data.

6. Cybersecurity and Data-Breach Disputes

A customer may bring a claim where confidential or personal information is exposed because of:

• inadequate security;
• unauthorized access;
• misconfiguration;
• credential compromise;
• insufficient encryption;
• failure to patch systems;
• negligent monitoring.

Possible claims include:

• breach of contract;
• negligence;
• breach of confidentiality;
• statutory data-protection claims;
• indemnity;
• compensation for regulatory penalties where legally recoverable.

The contract should therefore be examined for provisions concerning:

• security standards;
• incident notification;
• audit rights;
• subcontractors;
• encryption;
• access controls;
• breach response;
• allocation of regulatory responsibility.

7. Suspension and Termination Disputes

Cloud providers may suspend services because of:

• non-payment;
• security threats;
• prohibited use;
• legal requirements;
• excessive resource consumption;
• violation of acceptable-use policies.

The customer may argue that suspension was:

• contractually unauthorized;
• disproportionate;
• procedurally defective;
• commercially destructive;
• inconsistent with notice requirements.

The central question is normally the interpretation of the cloud agreement.

8. Intellectual-Property Disputes

Cloud computing involves multiple layers of IP:

• customer's software;
• customer's database;
• provider's platform;
• APIs;
• cloud infrastructure;
• third-party software;
• open-source components.

Disputes may concern whether the provider received sufficient rights to:

• host the customer's software;
• copy data;
• process data;
• make backup copies;
• modify software;
• use APIs;
• retain data after termination.

9. Vendor Lock-In and Data Portability

A major cloud dispute occurs when a customer wants to migrate from one provider to another.

Problems can arise concerning:

• proprietary formats;
• migration assistance;
• data-export fees;
• technical restrictions;
• deletion of old data;
• interoperability;
• transition periods.

A carefully drafted exit clause should specify:

• format of exported data;
• migration period;
• provider's assistance;
• charges;
• deletion certification;
• continued access during transition.

10. Limitation-of-Liability Clauses

Cloud providers commonly attempt to limit liability through:

• monetary caps;
• exclusion of consequential damages;
• exclusion of lost profits;
• exclusion of business interruption losses;
• service-credit mechanisms.

For example:

Customer loses ₹10 crore because of a cloud outage, but the contract limits liability to the previous three months' fees.

The enforceability and interpretation of such clauses become critical.

Courts generally examine the actual contractual language and applicable law rather than automatically treating a customer's claimed loss as recoverable.

11. Force Majeure

Cloud contracts commonly contain force-majeure provisions covering events beyond reasonable control.

These may include:

• natural disasters;
• earthquakes;
• floods;
• war;
• government action;
• telecommunications failure;
• power outages;
• labour disruptions.

AWS's customer agreement, for example, contains a force-majeure clause covering certain events beyond reasonable control and separately addresses dispute resolution and governing law.

However, force majeure is not automatically available merely because performance became difficult. The party relying upon it generally has to establish that the contractual requirements of the clause have been satisfied.

12. Arbitration in Cloud Computing Disputes

Arbitration is particularly important because cloud agreements frequently contain arbitration clauses.

Typical provisions specify:

• seat of arbitration;
• number of arbitrators;
• appointment procedure;
• governing law;
• institutional rules;
• confidentiality;
• emergency relief.

Indian courts generally examine the arbitration agreement and the scope of disputes before referring appropriate contractual disputes to arbitration.

The recent Ingram Micro matter demonstrates the practical importance of arbitration clauses in cloud-service billing disputes.

13. Jurisdictional Issues

Cloud computing is inherently cross-border.

For example:

Indian customer → Indian subsidiary/reseller → U.S. cloud provider → data centre in Singapore.

This can create questions concerning:

• which country's law applies;
• where the contract was performed;
• where the data was located;
• where the damage occurred;
• which court has jurisdiction;
• whether arbitration is mandatory.

Therefore, the governing-law and jurisdiction clause can be one of the most important provisions in a cloud contract.

14. Indian Tax and GST Issues

Cloud disputes may also involve taxation.

Questions can arise concerning whether payments constitute:

• royalty;
• fees for technical services;
• data-hosting services;
• intermediary services;
• export of services;
• imported services.

In Amazon Web Services, Inc. v. ACIT, the Delhi ITAT considered the tax treatment of cloud-service fees received from Indian customers and examined whether such receipts constituted royalty or fees for technical services under the Income-tax Act and India–U.S. DTAA.

A separate issue concerns the GST treatment of data-hosting services supplied to overseas cloud providers. Indian tax authorities have specifically considered whether a data-hosting provider is an "intermediary" under the IGST Act.

15. Important Indian Statutory Provisions

Information Technology Act, 2000

Relevant provisions may include:

• Section 43 – compensation for unauthorized access, downloading, disruption, etc.
• Section 43A – compensation relating to failure to protect sensitive personal data/information under the statutory framework.
• Section 65 – tampering with computer source documents.
• Section 72 – breach of confidentiality and privacy.
• Section 72A – disclosure of information in breach of lawful contract.

Their applicability depends upon the facts and the statutory framework in force at the relevant time.

Indian Contract Act, 1872

Cloud disputes frequently involve:

• Section 10 – validity of agreements;
• Section 37 – performance of contracts;
• Section 39 – refusal to perform;
• Section 55 – failure regarding time obligations;
• Section 62 – alteration/rescission;
• Section 73 – compensation for breach;
• Section 74 – stipulated compensation/penalty.

Section 73 is particularly important where the customer claims damages for cloud-service failure.

16. Six Important Case Laws

1. Progressive Infotech Ltd. v. Zenhill Pvt. Ltd. (Delhi District Court, 2023)

This is one of the most directly relevant Indian cases.

The plaintiff was an IT infrastructure service provider and reseller of AWS services. The defendant purchased AWS and managed services but eventually stopped making payments. The provider continued supplying services for some period and ultimately disconnected the services after substantial non-payment.

Principle

The case illustrates that cloud-service relationships are fundamentally contractual commercial relationships.

Important issues include:

• invoices;
• payment obligations;
• continued provision despite default;
• suspension/disconnection;
• contractual remedies.

Significance

It is particularly useful for answering questions concerning non-payment and termination of cloud services in India.

2. Ingram Micro Platform Technology India Pvt. Ltd. v. Creator Economy Tech Pvt. Ltd. (2026)

This is an especially significant recent Indian cloud-services dispute.

The dispute concerned AWS cloud infrastructure services supplied under an arrangement involving AWS pricing and usage. The claimant alleged outstanding invoices of approximately ₹7.19 crore and sought appointment of an arbitrator. The invoices incorporated sales terms containing an arbitration provision.

Principle

The matter demonstrates:

• cloud services can generate substantial metered contractual liabilities;
• invoices can incorporate contractual terms;
• acceptance and continued use of cloud resources can be important evidence;
• arbitration clauses can determine the dispute-resolution mechanism.

Significance

It is a useful contemporary authority for cloud billing and arbitration disputes.

3. Amazon Web Services, Inc. v. ACIT (Delhi ITAT, 2023)

The dispute concerned the tax treatment of cloud-computing fees received from Indian customers.

The Tribunal examined the nature of cloud computing, including the fact that customers access standardized computing, storage, database and related facilities without obtaining physical possession or control over the underlying infrastructure.

Principle

The case is important for distinguishing:

• access to cloud infrastructure;
• use of standardized automated services;
• transfer of rights in intellectual property;
• royalty characterization.

Significance

It demonstrates that cloud disputes are not limited to contract and technology law; tax characterization can itself become a major cloud-services dispute.

4. Amazon Internet Services Pvt. Ltd. v. Commissioner of CGST, Delhi East (2026)

This case involved the GST/service-tax characterization of data-hosting services provided in connection with AWS cloud infrastructure.

The dispute considered whether the data-hosting provider was an intermediary or was supplying hosting services on its own account.

Principle

A critical distinction exists between:

facilitating another person's supply

and

supplying one's own service.

Significance

This is important for determining:

• place of supply;
• export treatment;
• GST liability;
• intermediary classification.

5. HI Technology Corp. v. Quality Investment Properties Suwanee LLC

This U.S. case concerned a data-centre power outage.

The agreement contained an SLA under which the customer received a service credit when power was unavailable for a specified period. It also contained a consequential-damages limitation and a monetary liability cap. The customer nevertheless alleged substantial losses resulting from the outage.

Principle

Cloud/data-centre customers cannot necessarily recover every economic loss resulting from an outage.

The court must examine:

• SLA;
• service credits;
• liability limitations;
• exclusions;
• gross negligence/intentional misconduct provisions;
• contractual damage caps.

Significance

It is highly useful for understanding SLA and outage liability.

6. Parler LLC v. Amazon Web Services, Inc. (W.D. Washington, 2021)

Parler sought judicial relief requiring AWS to restore its web-hosting services. It asserted, among other claims, breach of contract and tort-related claims. The court considered whether emergency injunctive relief should be granted against AWS.

Principle

A customer seeking restoration of cloud services must establish the legal and equitable basis for extraordinary judicial intervention.

The case illustrates the importance of:

• contractual termination rights;
• acceptable-use provisions;
• injunction standards;
• likelihood of success;
• irreparable harm;
• public-interest considerations.

Significance

It is an important illustration of cloud-service suspension/termination disputes.

17. Additional Relevant Authority: Dakshin Haryana Bijli Vitran Nigam Ltd. v. Navigant Technologies Pvt. Ltd.

Although not a pure cloud-computing dispute, this Supreme Court case concerned a Service Level Agreement and arbitration in the technology-services environment.

The agreement contained an arbitration clause covering disputes connected with the contract, and the case addressed limitation in the context of arbitral proceedings.

Importance

It illustrates how technology-service disputes can become governed by:

• SLA provisions;
• arbitration clauses;
• limitation rules;
• procedural requirements under the Arbitration and Conciliation Act.

18. Common Claims in Cloud Disputes

19. Defences Available to Cloud Providers

A cloud provider may rely upon:

1. Contractual limitation

The provider may argue that liability is expressly capped.

2. SLA-exclusive remedy

The provider may argue that the customer agreed to receive only service credits.

3. Force majeure

The provider may argue that the failure resulted from an event beyond reasonable control.

4. Customer fault

The provider may establish that the problem resulted from:

• customer configuration;
• insecure credentials;
• customer software;
• customer negligence;
• improper use.

5. Contractual suspension right

The provider may rely upon an express right to suspend services.

6. Lack of causation

The provider may argue that the alleged business loss was not caused by the cloud provider.

7. Failure to mitigate

The provider may contend that the customer failed to take reasonable steps to minimize loss.

20. Customer's Remedies

Depending upon the contract and applicable law, a customer may seek:

• damages;
• refund;
• service credits;
• specific contractual relief;
• restoration of services;
• injunction;
• data recovery;
• indemnification;
• declaratory relief;
• arbitration;
• termination;
• return/export of data;
• compensation for proven losses.

However, contractual limitations can substantially restrict the available monetary remedies.

21. Key Legal Issues a Court/Arbitrator Examines

A cloud dispute is generally analysed through the following sequence:

Step 1 – Identify the contract

Master Service Agreement, Customer Agreement, SLA, purchase order, invoice and incorporated terms.

Step 2 – Identify the obligation

What exactly did the provider promise?

Step 3 – Establish breach

Was the promised service actually not provided?

Step 4 – Examine exclusions

Was the failure excluded by:

• force majeure;
• maintenance;
• customer fault;
• third-party infrastructure;
• security event?

Step 5 – Determine causation

Did the breach actually cause the claimed loss?

Step 6 – Determine damages

Was the loss foreseeable and legally recoverable?

Step 7 – Examine liability limits

Is there a contractual cap?

Step 8 – Determine forum

Court or arbitration?

Step 9 – Determine governing law

Which country's/state's law applies?

22. Difference Between Cloud Service Dispute and Ordinary IT Dispute

23. Special Importance of Evidence

In cloud litigation/arbitration, evidence may include:

• cloud usage logs;
• invoices;
• SLA reports;
• uptime records;
• API logs;
• access logs;
• security logs;
• incident reports;
• emails;
• support tickets;
• backup records;
• migration records;
• contractual amendments.

Because cloud services are technically complex, electronic records and expert evidence can become crucial in establishing breach and causation.

24. Practical Example

Suppose an Indian company purchases cloud infrastructure for ₹20 lakh per month.

The contract promises:

• 99.99% uptime;
• daily backup;
• four-hour incident response.

A major outage occurs for 18 hours, resulting in ₹5 crore of alleged business losses.

The customer sues for ₹5 crore.

The provider argues:

1. the outage resulted from force majeure;
2. the SLA provides only service credits;
3. consequential losses are excluded;
4. liability is capped at six months' fees;
5. the customer's own configuration contributed to the outage.

The court/arbitrator would therefore have to determine contract interpretation, SLA compliance, causation, force majeure, mitigation, liability limitations and damages rather than simply asking whether an outage occurred.

25. Six Core Case-Law Principles at a Glance

26. Conclusion

Cloud Computing Service Disputes are a specialized form of technology-contract litigation in which the principal legal questions usually concern service performance, SLAs, outages, billing, data loss, cybersecurity, suspension, termination, liability caps, indemnities, intellectual property, arbitration, jurisdiction and taxation.

The most important principle is that the cloud contract itself is usually the starting point. Courts and arbitrators examine what service was promised, what SLA applied, whether the provider or customer caused the failure, what exclusions apply, and what remedies the parties contractually agreed upon.

Indian litigation is increasingly encountering disputes involving actual cloud infrastructure and AWS-related services. The Progressive Infotech and Ingram Micro matters are particularly useful examples of disputes involving AWS services, payment obligations and contractual remedies.

Exam-ready definition

Cloud Computing Service Disputes are legal disputes arising from the provision, use, suspension, termination, billing, performance, security or management of cloud-based computing services, including disputes concerning service-level agreements, data protection, data loss, intellectual property, payment obligations, liability limitations, jurisdiction, arbitration and taxation. Such disputes are primarily determined by the governing cloud-service contract together with applicable contract, technology, data-protection, tax and arbitration laws.