Concentration of critical services on a few foreign cloud providers poses systemic risk. 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 November 12–13, 2026, Microsoft 365 went down worldwide. Microsoft blamed a fault in a network-capacity upgrade, and the outage disrupted email support at IndiGo, Akasa Air and Air India [1]. When a few foreign hyperscalers carry critical services, one upstream fault becomes a disruption across India. Yet Indian law sets no clear duty to report it or answer for it.
Why concentration creates systemic risk
- Single point of failure: a single error in one provider's change management spreads across many firms and sectors at once [1].
- Recurrence: CERT-In rated the July 2024 CrowdStrike-linked Windows outage "critical" [2]. Neither event was a cyber-attack.
- Spillover into security: CERT-In flagged phishing campaigns that exploited the 2024 outage [3].
- Regulatory blind spot: the CERT-In directions of April 28, 2022, issued under the IT Act, 2000, require reporting within six hours only for cyber incidents. An internal fault may fall outside them [1].
- Disclosure deficit: Microsoft's explanation was voluntary, and fuller details are still awaited [1]. Passengers are not parties to cloud contracts, so no SLA protects them.
Suggested framework
- Statutory basis: write an outage-accountability duty into the proposed Digital India Act, covering foreign providers that serve Indian users, instead of relying on delegated directions [1].
- Tiered reporting: keep the six-hour cyber window. Add a lighter "major outage" category, triggered by thresholds such as users affected or critical sectors hit. It would need a first notice and a time-bound root-cause analysis, while minor glitches stay exempt.
- Public advisories: make CERT-In's 2024 warning practice [3] a standard procedure for every major outage.
- Sectoral redundancy: regulators such as the Ministry of Civil Aviation should require a passenger-contact channel that does not depend on the main provider. Air India's rerouting shows this is feasible [1].
- Concentration mapping: MeitY should audit how much critical sectors depend on hyperscalers and require multi-cloud or exit plans.
Outage ──► Cyber incident? ──Yes──► CERT-In 6-hr report
│No
▼
Crosses threshold? ──Yes──► Notice → RCA → Public advisory
│No
▼
Contractual SLA only
Fig: Proposed tiered outage-accountability model
India's framework protects against breaches but not against loss of service. A proportionate, threshold-based regime in the Digital India Act, backed by sectoral redundancy, would make hyperscalers answerable to Indian users without burdening innovation. That would strengthen a resilient Digital India in line with SDG 9 (resilient infrastructure).
Sources
- 1How does India address service outages? — *The Hindu*, Nov 17, 2026 (explainer)Microsoft 365 outage and its cause; impact on airlines; CERT-In 2022 directions under the IT Act and the six-hour rule; voluntary disclosure
- 2CERT-In Advisory CIAD-2024-0035 (July 2024)CrowdStrike-linked outage rated "critical"
- 3CERT-In Current Activity CICA-2024-3308 (July 2024)phishing campaign exploiting the global outage