India platform blocking / intermediary liability

India's Telegram Block Converts Section 69A Into a Platform Kill Switch

A Delhi High Court ruling validating the six-day ban on 150 million users reshapes India's intermediary liability doctrine in ways that outlast the exam season.

India's Telegram Block: Scale vs. Scope People of Internet Research · India 150M Indian users blocked Telegram's entire Indian user base… ~1,300 URLs flagged by MeitY Telegram had already removed 900+ … 6 days Platform block duration Emergency order ran June 16–22; me… ~2.2M NEET-UG 2026 examinees Medical aspirants sitting the June… peopleofinternet.com

Key Takeaways

The Exam-Season Kill Switch

On June 16, 2026, India's Ministry of Electronics and Information Technology issued an emergency order under Section 69A of the Information Technology Act, 2000, directing all ISPs to block access to Telegram within one hour. The restriction lasted until June 22 — a day after the NEET-UG 2026 re-examination — with a separate mandate disabling Telegram's message-editing feature across India until June 30. Three days later, Delhi High Court Justice Tejas Karia dismissed Telegram's constitutional challenge, ruling the measure "lawful, proportionate, and procedurally valid" in Telegram FZ LLC v. Union of India (2026 SCC OnLine Del 4750).

The Problem Was Real

The case for intervention is not trivial. The original NEET-UG exam in May 2026 was cancelled after pervasive paper-leak allegations forced the National Testing Agency to scrap results affecting millions of medical aspirants scheduled for a June 21 re-examination. Before that re-test, fraud networks on Telegram employed a technically sophisticated scheme: channel administrators posted placeholder messages before the exam window, then exploited Telegram's editing feature to insert purported question-paper content afterward, while the original timestamp remained visible — manufacturing false evidence of pre-exam leaks that were sold to desperate students for substantial sums. The NTA and the Indian Cyber Crime Coordination Centre (I4C) flagged these networks to MeitY, citing the rapid reconstitution of banned channels through mirror accounts and automated bot ecosystems.

There is a genuine policy problem here. When a platform's architecture — its combination of mass-broadcast channels, timestamp-preserving edits, and automated bots — is systematically weaponised against a high-stakes public examination, regulatory inaction has real victims.

The Legal Leap

The government's solution, however, applied a sledgehammer where a scalpel was available. By the time MeitY issued the June 16 order, Telegram had already removed more than 900 of approximately 1,300 URLs flagged by authorities and had disabled over 150 bots associated with the fraud networks. The platform was not non-compliant — it was outpaced by the reconstitution velocity of the networks.

The court's reasoning to justify shutting down the entire platform rests on a significant doctrinal expansion. Section 69A has historically been understood — including in Shreya Singhal v. Union of India (2015 SC), which upheld it as "a narrowly drawn provision with adequate safeguards" — as authorising the blocking of specific information: individual URLs, posts, or pieces of content. Its procedural rules require committee review of individual blocking orders. Justice Karia departed from this content-centric reading by holding that Section 2(1)(v) of the IT Act — which defines "information" to include "codes, computer programmes, software and databases" — is broad enough to encompass an entire software application.

"An application falls within 'information,'" the court held. "Since platforms consist of these elements, the government may block access to an entire intermediary platform under Section 69A where circumstances warrant."

This moves Section 69A from content regulation to infrastructure regulation. Blocking a URL removes a specific piece of speech. Blocking a platform removes the speech of every person who uses it for any purpose.

150 Million Users for 1,300 URLs

Telegram claimed approximately 150 million Indian users were affected by the ban — every developer, journalist, activist, community group, and small business that used the platform for entirely lawful purposes. The court applied the four-part proportionality test from Anuradha Bhasin v. Union of India (2020 SC) — requiring legitimate aim, rational nexus, necessity, and least-restrictive means — finding that the short duration made the measure the "least restrictive alternative."

The reasoning is difficult to accept at face value. Six days of blanket suppression for 150 million users is treated as more proportionate than surgical remediation of 1,300 problematic URLs, even when the platform had already complied with 900 of them. The "least restrictive means" standard should ask: least restrictive compared to what alternatives? The court accepted the government's claim that targeted takedowns were insufficient without rigorous independent scrutiny of whether tools like court-issued injunctions, real-time API access for cybercrime units, or targeted operator suspensions had actually been exhausted.

The Architecture Trap

What makes the ruling consequential for India's digital future is the logic it validates: if a platform's technical architecture makes it difficult to eliminate all misuse through URL-level remediation, the platform itself qualifies for blocking. This is not a narrow carve-out for extraordinary emergencies — it is a general principle that inverts the intermediary liability bargain.

India has used Section 69A to block entire apps before. The June 2020 order blocked 59 Chinese apps including TikTok on national security grounds. A 2023 Karnataka High Court ruling in a case involving Twitter/X upheld account-level blocking under 69A. Each step has widened the provision's effective reach — from national security to public order to examination integrity, and from individual URLs to accounts to entire platforms with 150 million domestic users. The Telegram ruling marks the furthest extension yet.

What Proportionate Looks Like

A platform demonstrating good-faith compliance deserves a more targeted regulatory response. Proportionate tools exist: emergency injunctions requiring specific channel takedowns within defined hours; mandatory real-time API access enabling cybercrime units to flag and remove content without waiting for platform intermediation; liability calibrated to non-compliance with itemised orders rather than infrastructure-level shutdowns. The EU's Digital Services Act and the UK's Online Safety Act both provide frameworks for urgent content removal that treat platform-wide blocking as a last resort, not a first one.

The Precedent Outlasts the Exam

The six-day ban expired on June 22. Telegram is accessible again. But the doctrinal shift in Telegram FZ LLC v. Union of India has not. Future administrations need not find a new legal hook; Justice Karia's reasoning provides one. Any platform whose features can be exploited by bad actors faster than targeted remediation can work is now legally vulnerable to emergency shutdown under Section 69A — and that description fits every major communications service operating in India.

India's global credibility as a tech-forward democracy depends on regulatory tools that are surgical, evidence-based, and proportionate to actual harm. Platform-level blocking as a first-resort emergency measure is none of those things, even when the underlying fraud is real.

Sources & Citations

  1. SCC Online — Delhi HC Judgment (2026 SCC OnLine Del 4750)
  2. LiveLaw — Telegram's Challenge Filing, Delhi HC
  3. Tech Policy Press — Risks of Normalising Platform-Wide Blocking
  4. The Print — Delhi HC upholds Telegram block as 'least restrictive'
  5. The Federal — How Telegram ban expands scope of IT Act blocking powers
  6. LawBeat — Section 69A action held proportionate, HC ruling summary