How does India address service outages?
FlashcardsQuick reviseKey facts. One by one.Start →In this note
- At a Glance
- Why in the News
- Background & Evolution
- Core Static Facts
- Multi-Dimensional Analysis
- Recent Developments (last 12-18 months)
- Prelims Hooks (high-density factual bullets)
- Why a Fault Is Nobody's Job but an Attack Is CERT-In's
- How RBI Already Makes Banks Plan for a Vendor Going Down
- The Case Against Making CERT-In Track Every Outage
- Who Should Close the Gap, and How
- Anchors for Answers
- Mains Relevance
- Related Topics to Study Next
- NCERT Concepts to Revise
- Common Errors / Trap Areas
1. At a Glance
- Service outages are failures of digital or cloud services that people depend on, such as email, productivity suites and cloud platforms. They are not always caused by cyberattacks. Some come from technical faults, such as a bad network-capacity upgrade. [1]
- India's core problem: three sets of rules may apply to an outage, and each has a gap. The best-known, the CERT-In directions of 28 April 2022, cover attacks and intrusions but not outages caused by technical faults. [1]
- Why UPSC cares: the topic links cyber security governance (GS-III), regulatory accountability of Big Tech and cloud providers (GS-II), consumer protection and digital sovereignty / concentration risk in critical services such as aviation. [1]
2. Why in the News
- 12–13 November 2026: a Microsoft infrastructure problem cut off access to Microsoft 365 worldwide, including Outlook email. [1]
- Microsoft apologised and blamed a fault in an upgrade of its network capacity. More precise details were still awaited. [1]
- Impact in India: IndiGo and Akasa Air warned passengers that their email support was disrupted, and Air India rerouted its email. [1]
- The episode raised the question of whether companies serving lakhs of users in India have to account for such failures. [1]
3. Background & Evolution
- Information Technology Act, 2000: the parent law under which CERT-In issues its binding directions. [1]
- January 2023: a network outage took down Microsoft's Azure cloud platform and affected thousands of users in India. This is an earlier example of cloud concentration risk. [2]
- 28 April 2022: CERT-In issued directions requiring companies to report cyber incidents within 6 hours. [1]
- November 2026: the global Microsoft 365 outage exposed that these directions do not cover outages caused by technical faults. [1]
4. Core Static Facts
| Item | Fact |
|---|---|
| Nodal body | Indian Computer Emergency Response Team (CERT-In) [1] |
| Parent statute | Information Technology Act, 2000 [1] |
| Key instrument | CERT-In Directions dated 28 April 2022 [1] |
| Reporting window | Within 6 hours of a cyber incident [1] |
| Scope | Attacks and intrusions are covered; outages caused by technical faults are not [1] |
| Rules potentially applicable to outages | Three sets, and each has a gap [1] |
| Trigger incident | Microsoft 365 / Outlook, 12–13 Nov 2026, cause given as a fault in a network-capacity upgrade [1] |
| Indian sectors visibly hit | Civil aviation customer support (IndiGo, Akasa Air, Air India) [1] |
5. Multi-Dimensional Analysis
Legal / Constitutional
- India's incident-reporting law is built around security incidents, not reliability failures. A purely technical outage can therefore escape mandatory reporting under the CERT-In directions. [1]
- The source article finds a gap in each of the three rule-sets that may apply, so there is no single binding outage-disclosure duty. [1]
Economic
- Firms that rely on one productivity or cloud vendor face business-continuity risk. Airlines had to warn customers or reroute email. [1]
- Repeated incidents point to systemic concentration risk across sectors: Azure in 2023 [2] and Microsoft 365 in 2026 [1].
Ethical / Governance
- Accountability asymmetry: services that lakhs of people rely on can fail, and the only explanation may be a voluntary apology. [1]
- Microsoft explained the cause only in general terms ("fault in an upgrade of network capacity"), with more precise details still pending. [1]
Scientific / Technological
- A cyber incident (attack or intrusion) is different from an operational outage (fault in a change or upgrade). The two need different regulatory tools. [1]
- Single points of failure in network infrastructure can spread globally. Azure in 2023 was a network outage [2], and Microsoft 365 in 2026 followed a network-capacity upgrade [1].
Administrative
- Mandatory reporting to CERT-In is triggered only by incidents within its scope. Outage information therefore depends on the provider's own disclosures. [1]
6. Recent Developments (last 12-18 months)
- 12–13 Nov 2026: global Microsoft 365 / Outlook outage. Microsoft apologised and pointed to a fault in a network-capacity upgrade. [1]
- Nov 2026: IndiGo and Akasa Air issued passenger alerts about email-support disruption, and Air India rerouted email. [1]
- 17 Nov 2026: The Hindu published an explainer on the gaps in India's outage-accountability rules and on how other countries hold cloud providers accountable. [1]
7. Prelims Hooks (high-density factual bullets)
- CERT-In directions on cyber-incident reporting were issued on 28 April 2022. [1]
- They were issued under the Information Technology Act, 2000. [1]
- Reporting deadline: 6 hours. [1]
- The directions cover attacks and intrusions. [1]
- Outages caused by technical faults fall outside them. [1]
- Three sets of rules may apply to service outages in India, and each has a gap. [1]
- The Microsoft 365 global outage took place on 12–13 November 2026. [1]
- Microsoft's stated cause: a fault in an upgrade of its network capacity. [1]
- Indian airlines affected: IndiGo, Akasa Air (alerts) and Air India (rerouted email). [1]
- An earlier Azure outage in January 2023 was caused by a network outage. [2]
- Outlook is part of the Microsoft 365 productivity suite. [1]
8. Why a Fault Is Nobody's Job but an Attack Is CERT-In's
- India's law asks "was this an attack?", not "did the service stop working?"
- CERT-In's 6-hour duty is triggered by attacks and intrusions [1].
- A failed upgrade can cause the same harm to users as an attack: no email, no airline support desk. But it creates no duty to report [1].
-
So the law looks at what caused the failure. It does not look at how much harm the failure did.
-
The result: the government learns about an outage the same way the public does
- With no reporting duty, the only account of the November 2026 outage is Microsoft's own apology [1].
- That apology named the cause only in general terms. Precise details were still awaited [1].
-
No Indian body can ask for a root-cause report (a written account of exactly what went wrong and why), because no rule makes the outage its business.
-
The same failure keeps coming back, and nothing changes after it
- January 2023: a network outage took down Azure for thousands of users in India [2].
- July 2024: a global IT outage disrupted Indian flyers. In India, the damage stayed with firms that used the one vendor involved [4].
- November 2026: IndiGo, Akasa Air and Air India were hit again, this time through Microsoft 365 [1].
- Three big incidents in under four years, and the reporting rule still does not cover a technical fault [1].
9. How RBI Already Makes Banks Plan for a Vendor Going Down
- One Indian regulator has already handled this, but from the customer's side
- RBI makes the firms it regulates (banks and other regulated entities, or REs) keep business continuity and disaster recovery plans (BCP/DR, meaning a tested plan to keep working when a system fails) for the IT services they outsource, including cloud [3].
-
Banks must also make their service providers keep a documented and tested BCP/DR framework [3].
-
Why this matters for the outage debate
- RBI does not regulate Microsoft. It regulates the bank that buys from Microsoft, and that bank must carry the risk on paper [3].
-
This route works without any new law on foreign cloud firms. Indian regulators already have power over the Indian buyer.
-
Its limit: it covers only sectors that have a strong regulator for these risks
- The airlines hit in 2024 and 2026 had to fall back on manual work-arounds and email rerouting [1][4].
- The sources show no outage-planning rule for them like RBI's, so each airline decides its own backup on its own.
10. The Case Against Making CERT-In Track Every Outage
- The strongest objection: this would bury a security agency in routine breakdowns
- CERT-In exists to respond to attacks. Its 6-hour window is built for threats that may spread to others [1].
- Cloud services slow down or fail in small ways all the time. If every one of these had to be reported, the reports that really matter (actual intrusions) could get lost in the pile.
-
Industry already called the 6-hour rule tight for attacks alone. Adding faults would make that burden heavier.
-
What the objection gets right
- Not every outage is a national-security matter. A 6-hour, all-cases rule copied over to faults would be the wrong tool [1].
-
A cyber incident and an operational outage need different regulatory tools [1].
-
What it gets wrong
- It treats "report to CERT-In" and "report to no one" as the only two choices.
- The real gap is the large outage: one that hits lakhs of users or a critical sector such as aviation [1]. That can be covered by a threshold (a minimum size of outage that triggers the duty), with a longer deadline, sent to the sector regulator rather than to CERT-In.
- The RBI model shows a sector regulator can carry this duty without CERT-In [3].
11. Who Should Close the Gap, and How
- MeitY: write outage reporting into the successor to the IT Act
- The IT Act, 2000 is the parent law of CERT-In's directions. Those directions only cover security incidents [1].
-
The proposed Digital India Act is the natural place to add a separate duty: large technical-fault outages must be reported, with a root-cause report after the event.
-
Sector regulators: copy RBI's continuity rule for critical sectors
- RBI already makes its regulated entities plan for an outsourced IT service failing, and makes their vendors test their backup plans [3].
-
Aviation was hit in 2024 and again in 2026 [4][1]. Its regulator could ask airlines for a similar tested fallback for passenger-facing systems.
-
Large Indian buyers: stop depending on a single vendor
- In July 2024, Indian firms that did not use the one affected vendor got through mostly unharmed [4].
- Concentration risk (when many users rely on one provider, so one failure hits all of them at once) falls when critical functions have a second route. Air India rerouting its email in 2026 is a small example of this [1].
12. Anchors for Answers
- Data: January 2023 Azure network outage affected thousands of users in India [2]; three sets of rules may apply to outages in India, and each has a gap [1]
- Report/Committee: RBI Master Direction on outsourcing of IT services (2023), which requires BCP/DR plans for outsourced IT including cloud, and tested BCP/DRP frameworks at service providers [3]
- Law/Case: IT Act, 2000 and the CERT-In Directions of 28 April 2022: 6-hour reporting for attacks and intrusions, with technical-fault outages excluded [1]
- Comparison: July 2024 global outage: in India, the damage stayed with enterprises that used the affected vendor, which shows how dependence on one vendor spreads failure [4]
13. Mains Relevance
- GS-III: Challenges to internal security through communication networks; basics of cyber security; IT and awareness in computers.
- GS-II: Government policies and interventions; regulatory bodies; accountability and transparency.
- GS-IV (minor): Corporate governance and accountability.
- Question stems: 1. India's cyber-incident reporting framework focuses on security breaches but ignores reliability failures. Critically examine this in the light of recent global cloud outages. (15 marks) 2. Dependence on a few global cloud service providers creates systemic risk for critical sectors. Suggest a regulatory framework for outage accountability in India. (15 marks) 3. Discuss the role and limitations of CERT-In in ensuring the resilience of India's digital public and private infrastructure. (10 marks)
14. Related Topics to Study Next
- CERT-In: mandate and powers. It is the nodal body whose 2022 directions are the main reporting instrument.
- IT Act, 2000 and the proposed Digital India Act. These are the parent and successor frameworks where outage accountability could be written in.
- Digital Personal Data Protection Act, 2023. It is the other "breach-centric" regime and a useful comparison on reporting duties.
- NCIIPC and Critical Information Infrastructure. Outages in critical sectors raise resilience questions.
- Consumer Protection Act, 2019 and deficiency in service. It is one possible remedy route for affected customers.
- Data localisation and digital sovereignty. These connect to concentration risk on foreign cloud providers.
- The July 2024 global IT outage. It is the comparable precedent that hit Indian airlines and banks.
- EU DORA / NIS2. These are foreign models of mandatory ICT-incident and outage reporting.
15. NCERT Concepts to Revise
- CERT-In (Polity): Nodal agency whose April 2022 directions are India's main incident-reporting rule, yet exclude technical-fault outages.
- Cyber security (Polity): The outage is set against India's cyber incident reporting and response framework, which covers attacks but not faults.
- Concentration risk (Economy): Airlines and many firms relied on one Microsoft service, so a single failure hit them all together.
- Systemic risk (Economy): Repeated Azure and Microsoft 365 failures show how one provider's fault can cascade across many sectors.
- Resilience (Economy): Outages test whether services keep working and recover quickly, which is different from simply rarely failing.
- Cloud computing (Economy): Azure and Microsoft 365 are cloud services; understanding them explains why one network fault spreads worldwide.
- Accountability (Polity): Providers serving lakhs of Indian users face no binding duty to explain failures beyond a voluntary apology.
- Transparency (Polity): Outage causes were disclosed only in general terms, raising the question of mandatory disclosure of what went wrong.
- Digital sovereignty (Polity): Dependence on foreign-headquartered cloud providers for critical services links outages to India's control over digital infrastructure.
- National Critical Information Infrastructure Protection Centre (Polity): Outages in critical sectors like aviation raise questions about protecting critical information infrastructure.
- Consumer Protection Act, 2019 (Economy): A possible remedy route for customers affected by service failures, including deficiency in service claims.
- Deficiency in service (Economy): Affected customers could seek compensation if an outage amounts to a shortfall in service quality.
- Data localisation (Economy): Storing and processing data within India is a policy response linked to reliance on foreign cloud providers.
16. Common Errors / Trap Areas
- Assuming every outage must be reported to CERT-In. The directions cover attacks and intrusions, not technical-fault outages. [1]
- Wrong date. The CERT-In directions are dated 28 April 2022, not 2020 or 2023. [1]
- Wrong window. The deadline is 6 hours, not 24 or 72 hours as in some foreign regimes. [1]
- Mixing up incidents: Azure network outage (Jan 2023) [2], Microsoft 365 / Outlook outage (Nov 2026) [1] and the July 2024 CrowdStrike-linked Windows outage. Each had a different cause and different affected services.
- Wrong parent law. The CERT-In directions flow from the IT Act, 2000, not the DPDP Act, 2023. [1]
Not verified from the allowed sources (check before using):
- The specific provision is commonly given as Section 70B(6) of the IT Act.
- The directions are commonly said to have taken effect on 27 June 2022.
- The July 2024 outage is commonly attributed to a CrowdStrike update.
Sources
- 1How does India address service outages? — The Hindu (N.V. Geetha, 17 Nov 2026)thehindu.com · tier 4
- 2Microsoft outage impacts thousands in India — Business Standard (Jan 2023)business-standard.com · tier 4
- 3Reserve Bank of India — Master Directions on outsourcing of information technology services (cloud, BCP/DR requirements)rbi.org.in · tier 1
- 4Microsoft outage: Indian flyers impacted, other services largely unaffected — Business Standard (19 July 2024)business-standard.com · tier 4