·The Hindu

How does India address service outages?

FlashcardsQuick reviseKey facts. One by one.Start →
In this note
  1. At a Glance
  2. Why in the News
  3. Background & Evolution
  4. Core Static Facts
  5. Multi-Dimensional Analysis
  6. Recent Developments (last 12–18 months)
  7. Prelims Hooks
  8. Why the Six-Hour Rule Cannot See an Upgrade Gone Wrong
  9. The Case for Leaving Outages to Contracts — and Where It Fails
  10. Aviation Has Now Been Hit Twice by Faults Abroad
  11. What Should Change, and Who Should Do It
  12. Anchors for Answers
  13. Mains Relevance
  14. Related Topics to Study Next
  15. NCERT Concepts to Revise
  16. Common Errors / Trap Areas
Practice
6 questions on this article
Check the answer for each question, or reveal all at once.
Practice MCQs →

1. At a Glance

  • The issue: whether large digital/cloud service providers that lakhs of people depend on must, under Indian law, report and answer for service outages, as opposed to cyber-attacks [1].
  • Trigger case: a global Microsoft 365 outage on November 12–13, 2026 also disrupted Indian businesses, including airlines [1].
  • Core point: three sets of rules apply in India and each one has a gap [1]. The main one is the CERT-In directions of April 28, 2022, issued under the Information Technology Act, 2000, which require cyber incidents to be reported within six hours [1].
  • UPSC relevance: GS-III (cyber security, critical information infrastructure), GS-II (regulation, accountability of private platforms), and Ethics/Governance (corporate accountability).

2. Why in the News

  • November 12–13, 2026: a fault in Microsoft infrastructure, not yet fully explained, stopped customers worldwide from reaching Microsoft 365, including Outlook email [1].
  • Microsoft apologised during the outage and blamed a fault in an upgrade of its network capacity. More precise details are still expected [1].
  • Impact in India: IndiGo and Akasa Air warned passengers that their email support was disrupted. Air India rerouted its email [1].
  • The incident raised the question of whether Indian law required Microsoft to report the outage, and what Indian customers can do [1].

3. Background & Evolution

  • 2000: the Information Technology Act, 2000 was enacted. It is the parent law under which CERT-In issues directions [1].
  • April 28, 2022: CERT-In issued directions under the IT Act requiring companies to report cyber incidents within six hours [1].
  • November 2026: the Microsoft 365 outage exposed gaps in all three applicable sets of rules [1].
  • Not confirmed from whitelisted sources (verify before use): the 2022 directions were issued under Section 70B(6) of the IT Act and took effect 60 days later (June 27, 2022). The DPDP Rules, 2025 (notified November 2025) include a 72-hour breach-report requirement. These come from law-firm commentary that the whitelist does not allow, so they are deliberately left uncited.

4. Core Static Facts

Item Fact Cite
Nodal cyber agency Indian Computer Emergency Response Team (CERT-In) [1]
Parent statute Information Technology Act, 2000 [1]
Key instrument CERT-In directions dated April 28, 2022 [1]
Reporting window 6 hours to report cyber incidents [1]
Number of applicable rule-sets Three, each with a gap [1]
Outage dates Nov 12–13, 2026 [1]
Services affected Microsoft 365 productivity suite, including Outlook [1]
Stated cause Fault in an upgrade of network capacity [1]
Indian sectors hit Aviation: IndiGo, Akasa Air, Air India [1]
  • Key terms:
  • A cyber incident is a security event, which the CERT-In regime covers.
  • A service outage is a loss of availability that may have no malicious cause.
  • The difference between the two is the main gap under discussion [1].

5. Multi-Dimensional Analysis

Legal / Constitutional

  • The CERT-In directions sit under the IT Act, 2000. They are delegated directions, not a separate outage law [1].
  • The six-hour rule targets cyber incidents. An outage caused by an internal fault, such as an upgrade error, may fall outside it. This is the "gap" the article points to [1].
  • India has no single statute that sets an outage-reporting or service-level accountability duty for cloud providers. That is why three overlapping rule-sets apply [1].

Economic

  • Businesses depend heavily on foreign cloud and productivity platforms. One upstream fault spread to Indian airlines' customer-support channels [1].
  • Indian enterprise customers have limited remedies beyond their contracts, which raises the question of what options they have [1].

Governance / Accountability

  • Microsoft's apology and cause attribution were voluntary, and full details were still pending. This shows there is no binding duty to disclose to customers or regulators [1].
  • The article asks how other countries hold cloud companies accountable, pointing to India's comparative regulatory deficit [1].

Scientific / Technological

  • The failure came from a network capacity upgrade [1]. Change-management errors, not attacks, are a major cause of hyperscale outages.
  • When many firms depend on one provider, a single failure takes them all down together. This is a single point of failure (concentration risk).

Strategic / Security

  • When foreign hyperscalers serve critical sectors such as aviation, outage resilience becomes a matter of digital sovereignty and critical information infrastructure policy [1].

6. Recent Developments (last 12–18 months)

  • Nov 12–13, 2026: global Microsoft 365/Outlook outage, with disruption in India [1].
  • Nov 2026: IndiGo and Akasa Air issued passenger advisories, and Air India rerouted email [1].
  • Nov 17, 2026: The Hindu published an explainer on the gaps in India's outage-accountability framework [1].
  • Verify: notification of the DPDP Rules, 2025 in November 2025, with a phased rollout. This is relevant to breach reporting, but no whitelisted source was retrieved for it.

7. Prelims Hooks

  • CERT-In issued its cyber-incident reporting directions on April 28, 2022 [1].
  • The directions were issued under the Information Technology Act, 2000 [1].
  • Reporting window under the CERT-In directions: six hours [1].
  • Full form: CERT-In = Indian Computer Emergency Response Team [1].
  • Three sets of Indian rules apply to service outages, and each has a gap [1].
  • The Microsoft 365 outage ran from November 12 to 13, 2026 [1].
  • Microsoft blamed the outage on a fault in an upgrade of its network capacity [1].
  • Outlook email was among the services affected [1].
  • Indian airlines that reported disruption: IndiGo, Akasa Air (support email); Air India (rerouted email) [1].
  • Verify before memorising: CERT-In's power to issue directions → Section 70B of the IT Act. DPDP breach detailed report → 72 hours.

8. Why the Six-Hour Rule Cannot See an Upgrade Gone Wrong

  • The rule is triggered by an attack, not by a breakdown
  • The CERT-In directions ask companies to report cyber incidents within six hours [1].
  • Microsoft says its outage came from a fault while upgrading its own network capacity [1]. Nobody attacked it.
  • So the event that hurt Indian users most may never fall under the rule written to deal with digital emergencies.

  • Even when a report is made, it goes to the government, not to the user

  • The six-hour report goes to CERT-In, which uses it to respond to threats [1].
  • The customer gets nothing under this rule. It does not give the airline or its passengers any right to an explanation.
  • Indian customers only learned the cause because Microsoft chose to apologise, and the full details are still awaited [1].

  • 'Not an attack' can only be known later

  • When a service goes down, its users cannot tell at first whether it is a bug or a hack.
  • In July 2024, soon after the CrowdStrike outage, CERT-In warned that criminals were using it to send phishing emails (fake messages that steal passwords) to CrowdStrike users [2].
  • So an outage with an innocent cause quickly became a security problem. A rule that covers only security events misses this link.

9. The Case for Leaving Outages to Contracts — and Where It Fails

  • The strongest argument against a new outage law
  • Large firms like airlines sign contracts with cloud providers. These contracts include an SLA (service-level agreement: a promise of how often the service will be up, with penalties if it is not).
  • Providers already lose money and reputation when they go down, so they have reasons to fix faults fast without a law.
  • A six-hour reporting duty for every small glitch would flood CERT-In with reports and take engineers' time just when they are busy fixing the fault.

  • What this argument gets right

  • Treating every outage like a cyber attack would be the wrong design. Most short glitches do not need a regulator.
  • Any new duty should be limited to large outages that hit many users or critical sectors.

  • Where it fails: the people harmed are not parties to the contract

  • The airline has a contract with Microsoft. The passenger does not.
  • When IndiGo's and Akasa Air's email support went down, passengers lost their way of contacting the airline [1]. No SLA protects them.
  • This is an externality (a cost that falls on someone outside the deal). Contracts cannot fix costs that fall on people who never signed them.

  • Where it fails: the provider decides how much to say

  • Microsoft gave its cause during the outage, but more precise details are still expected [1].
  • Under a contract, the provider decides how much it says and when. A regulator cannot check whether India's lessons from the failure are complete.

10. Aviation Has Now Been Hit Twice by Faults Abroad

  • The same sector, the same kind of failure
  • In July 2024, a faulty CrowdStrike update affected Microsoft systems worldwide. Indian flyers were hit, while other services were largely unaffected [3].
  • In November 2026, a Microsoft 365 fault again disrupted IndiGo, Akasa Air and Air India [1].
  • Neither event was a cyber attack. Both started outside India, in systems Indian airlines do not control.

  • Why aviation keeps showing up

  • Airlines run on time-bound customer contact: check-in, rebooking, support emails.
  • Even an hour of downtime turns into stranded or confused passengers. A bank or a factory might absorb the same hour more quietly.

  • One airline's response shows backups are possible

  • Air India rerouted its email, while IndiGo and Akasa Air warned passengers that email support was disrupted [1].
  • The difference lies in preparation inside each airline, not in the outage. Today, no rule tells airlines how much backup they must keep.

11. What Should Change, and Who Should Do It

  • MeitY and CERT-In: create a separate, lighter outage category
  • Keep the six-hour window for cyber incidents [1].
  • Add a second duty only for large outages, for example those hitting critical sectors like aviation. It should cover a short first notice and a later root-cause analysis (a written account of what failed and why).
  • This answers the over-reporting worry. Small glitches stay outside the rule, and big failures get explained in full rather than voluntarily [1].

  • CERT-In: make public outage advisories a standard practice

  • After the 2024 outage, CERT-In did warn users about phishing that used the outage [2].
  • That was a one-time response. Writing it into a standard procedure would mean every major outage triggers a public safety warning, whatever its cause.

  • Ministry of Civil Aviation: require backup channels for passenger contact

  • Air India's rerouted email shows a fallback can work [1].
  • Airlines could be asked to keep at least one passenger contact channel that does not depend on the same cloud provider. That cuts the single point of failure at the airline's end.

  • MeitY: use the proposed Digital India Act to set the duty in law

  • The CERT-In directions are delegated directions under the IT Act, 2000 [1]. They depend on how that Act is read.
  • An outage-accountability duty set in the planned replacement law would rest on clear legal ground and cover foreign hyperscalers (very large cloud companies) that serve Indian users.

12. Anchors for Answers

  • Data: Two non-malicious, foreign-origin outages hit Indian aviation within about two and a half years: CrowdStrike/Microsoft in July 2024 and Microsoft 365 on November 12–13, 2026 [3][1]
  • Law/Case: Information Technology Act, 2000; CERT-In directions of April 28, 2022 (six-hour cyber-incident reporting) [1]
  • Comparison: CERT-In's July 2024 phishing warning after the CrowdStrike outage shows a non-malicious outage turning into a security risk [2]
  • Scheme: Digital India: as more services move online, an outage becomes a service-delivery failure and not just a technical fault

13. Mains Relevance

14. Related Topics to Study Next

  • IT Act, 2000 (Sections 70, 70A, 70B): the statutory base for CERT-In and for protected systems / critical information infrastructure.
  • NCIIPC: protects critical information infrastructure, as distinct from CERT-In.
  • Digital Personal Data Protection Act, 2023 & DPDP Rules, 2025: a parallel breach-notification regime.
  • Telecommunications Act, 2023: service-disruption and suspension provisions for telecom.
  • National Cyber Security Policy, 2013 / proposed national cyber security strategy: the policy framework.
  • Digital India Act (proposed): the planned replacement for the IT Act, which could fill accountability gaps.
  • Data localisation & cloud empanelment (MeitY): sovereignty and concentration risk.
  • July 2024 global IT outage (CrowdStrike update): an earlier example of a non-malicious mass outage.

15. NCERT Concepts to Revise

  • CERT-In (Polity): The CERT-In directions of 2022 are the main rule-set, requiring cyber incidents to be reported within six hours.
  • Ministry of Electronics and Information Technology (Polity): MeitY administers the IT Act and houses CERT-In, so it is the ministry that could close these gaps.
  • Single point of failure (Economy): One Microsoft fault disrupted many Indian firms at once, as the airline email problems showed.
  • Concentration risk (Economy): Indian businesses depend heavily on a few foreign cloud providers, so one upstream failure spreads widely.
  • Systemic risk (Economy): A single provider's failure triggering wider knock-on disruption across sectors is the systemic risk the Mains questions ask about.
  • Accountability (Polity): The article asks whether cloud providers must answer to regulators and customers for outages, which is an accountability question.
  • Transparency (Polity): Microsoft's apology and cause were voluntary; no law forces it to disclose outage details.
  • Digital Personal Data Protection Act 2023 (Polity): It is a parallel breach-notification regime and one of the rule-sets with gaps for outages.
  • DPDP Rules 2025 (Polity): These rules set the breach-reporting timelines that aspirants often confuse with CERT-In's six hours.
  • Telecommunications Act 2023 (Polity): It covers service disruption in telecom and may be one of the overlapping rule-sets.
  • Data localisation (Economy): Storing data inside India is a policy response to dependence on foreign cloud providers.
  • Sovereignty (Polity): Relying on foreign hyperscalers for critical sectors like aviation raises digital sovereignty concerns.
  • Governance (Polity): The note is about how rules and regulation govern private digital providers and make them answerable.
  • Digital India (Polity): Digital India drives dependence on digital services, which makes outage resilience a policy concern.

16. Common Errors / Trap Areas

  • Cyber incident ≠ outage: the six-hour CERT-In rule is about cyber incidents. Do not assume it automatically covers every service failure [1].
  • Wrong parent law: the CERT-In directions come under the IT Act, 2000, not the DPDP Act or the Telecom Act [1].
  • Date confusion: directions issued April 28, 2022. The commonly cited effective date is about two months later (verify). Do not mix the two.
  • 6 hours vs 72 hours: 6 hours is the CERT-In cyber-incident window [1]. 72 hours is the commonly cited DPDP breach-report window (verify). Aspirants often swap them.
  • CERT-In vs NCIIPC: CERT-In is the national incident-response agency. NCIIPC handles critical information infrastructure protection. They are different bodies.

Sources

  1. 1How does India address service outages? (N.V. Geetha), The Hindu, Nov 17, 2026, Page 8, Delhi editionthehindu.com · tier 4
  2. 2Phishing attacks targetting CrowdStrike users after global outage: CERT-Inbusiness-standard.com · tier 4
  3. 3Microsoft outage: Indian flyers impacted, other services largely unaffectedbusiness-standard.com · tier 4
At the end · practice MCQs
6 questions on this article
Check the answer for each question, or reveal all at once.
Practice MCQs →

Mains Q&A on this note

NCERT concepts in this note

Also on 17 November

All 17 November articles →