Dependence on a few global cloud service providers creates systemic risk for critical sectors. Suggest a regulatory framework for outage accountability in India.
New · District CollectorCan you hold the district for 72 hours?Floods, a heatwave, an outbreak, a grievance queue. Take the decisions, see the consequences.Play →On 12–13 November 2026 a single Microsoft infrastructure fault took Microsoft 365 and Outlook offline worldwide. In India, IndiGo and Akasa Air had to warn passengers that email support was disrupted, and Air India rerouted its email [1]. When a few providers serve many critical users, one failure spreads to all of them. Yet India has no binding duty to account for such failures.
Why concentration creates systemic risk
- Single point of failure: a fault in one network-capacity upgrade spread across countries and sectors at once [1].
- Law looks at the cause, not the harm: the CERT-In Directions of 28 April 2022, issued under Section 70B(6) of the IT Act, 2000, require cyber incidents to be reported within 6 hours [2]. Outages caused by technical faults fall outside them [1].
- Information asymmetry: the state learns what happened from the provider's voluntary apology, which named the cause only in general terms [1].
- Fragmented rules: three sets of rules may apply to outages, and each has a gap [1].
Suggested regulatory framework
- Legal basis: put a separate outage-reporting duty in the proposed Digital India Act, kept apart from security-incident reporting.
- Threshold-based duty: only large outages, measured by users affected, duration or critical sector, trigger reporting. The deadline should be longer than 6 hours, followed by a mandatory root-cause analysis (RCA).
- Sector regulator as nodal point: this avoids flooding CERT-In, a security agency, with routine breakdowns. TRAI already makes telecom providers report major outages with root causes and corrective action [3].
- Regulate the Indian buyer: RBI's IT Outsourcing Directions, 2023 require regulated entities to keep business-continuity and disaster-recovery (BCP/DR) plans for outsourced IT, including cloud, and make their vendors keep tested BCP/DR frameworks [4]. Aviation, power and health regulators should adopt similar rules.
- Multi-vendor resilience: critical functions should have a second route. Air India rerouting its email is a small example [1].
- Consumer redress: the Consumer Protection Act, 2019 ("deficiency in service") can be paired with mandatory disclosure of service-level agreements and compensation norms.
Flow: Outage → threshold test → report to sector regulator → public RCA summary → corrective action or penalty.
Concentration risk cannot be removed, but it can be governed. A framework that looks at harm rather than cause would combine threshold reporting, buyer-side continuity rules and diversified sourcing. It would make global providers answerable in India without overloading CERT-In, and would advance SDG 9's goal of resilient infrastructure.
Sources
- 1How does India address service outages? — The Hindu explainer (17 Nov 2026)the November 2026 Microsoft 365 outage and its cause; the airlines affected; technical-fault outages excluded from the CERT-In directions; three sets of rules, each with a gap; Microsoft's apology
- 2CERT-In Directions under Section 70B(6) of the IT Act, 2000 (No. 20(3)/2022-CERT-In, 28 April 2022)6-hour reporting duty for cyber incidents
- 3TRAI Direction on reporting of network outages (28 March 2023)telecom providers must report outages with root causes and corrective action
- 4RBI Master Direction on Outsourcing of Information Technology Services (2023)BCP/DR plans for outsourced IT, including cloud; tested BCP/DR frameworks at service providers