A verdict built on a hard case
On June 19, 2026, the Delhi High Court dismissed Telegram's constitutional challenge to a week-long nationwide shutdown of the platform, ordered by India's Ministry of Electronics and Information Technology (MeitY) on June 16 ahead of the NEET-UG medical entrance re-examination. In a 39-page ruling in Telegram FZ LLC & Anr. v. Union of India & Ors. (W.P.(C) 8259/2026), Justice Tejas Karia held that the blocking order — which cut off a platform Telegram says serves over 150 million Indians — was the "least restrictive measure" available and satisfied the constitutional test of proportionality.
The case is genuinely hard, and the government's position deserves to be stated fairly before it's contested. NEET-UG, India's national undergraduate medical entrance exam, had already been thrown into crisis once this year after paper leaks forced a re-test for roughly 2.2 million candidates. The National Testing Agency told MeitY on May 22 that fraud networks were using Telegram's large public channels and bot ecosystem to circulate fabricated "leaked paper" claims and run payment scams targeting anxious families. Critically, the government says it tried the narrower route first: MeitY notified 1,300 specific URLs for takedown, and Telegram disabled only 900 of them, with the remainder resurfacing through what the court's ruling calls Telegram's "mirror channel" architecture — new channels that reconstitute a taken-down one within minutes. The court also credited a MeitY argument that Telegram's message-editing feature let bad actors alter timestamps to manufacture false evidence of leaks, which is why the government paired the platform block with a separate order disabling message-editing until June 30. On those facts, a full block for a bounded week, ahead of a specific exam date, framed by the court as protecting the integrity of a national examination for millions of students, is not an unreasonable emergency response.
Where the reasoning goes further than the emergency required
The problem is not the outcome for Telegram this particular week. It's the legal reasoning the court used to get there. Section 69A of the Information Technology Act, 2000 — the provision the Supreme Court upheld in Shreya Singhal v. Union of India (2015) specifically because it read as a narrow, content-specific blocking power with procedural safeguards — authorizes the government to block "information." Justice Karia's ruling interprets that term to include "the software architecture, databases and the entirety of the programmatic ecosystem which constitute an application," and on that basis held that Section 69A reaches not just posts or channels but an entire platform. As Amber Sinha writes at Tech Policy Press, this is the first time an Indian court has validated a full-platform block under Section 69A, and it does so without directly reconciling that reading with Shreya Singhal's narrower framing of the same provision.
That distinction matters because Shreya Singhal is the load-bearing precedent that has kept Section 69A defensible for over a decade. It survived constitutional scrutiny — while its sibling Section 66A did not — precisely because the Supreme Court read it as reaching identified content through a reasoned, appealable order, not as a general switch for taking infrastructure offline. Collapsing "information" into "the entirety of the programmatic ecosystem" doesn't just resolve the Telegram case; it hands the executive a template for full-platform blocking wherever narrower measures can be shown, after the fact, to have been imperfectly effective. Given how routinely takedown compliance is partial on any platform with user-generated content at scale, that's a low bar to clear again.
The precedent problem, not the week-one problem
The practical risk isn't that MeitY will casually re-block Telegram. It's the incentive structure the ruling creates for every platform operating in India. When a full-platform shutdown is judicially validated as "least restrictive" — rather than treated as the last resort after due exhaustion of content-specific tools with a genuine evidentiary record on the platform's non-cooperation — the credible threat of a shutdown becomes a negotiating tool the government can raise short of ever using it. Platforms facing that threat have every incentive to over-comply with informal requests they might otherwise contest, well before any court gets to review the underlying justification. A rule meant for exam-fraud emergencies can migrate quickly to other "public order" justifications, a category broad enough that the guardrail against overreach was always supposed to be procedural: a reasoned order, subject to genuine judicial scrutiny of necessity, not just of intent.
A narrower path was available
Proportionate regulation doesn't require accepting platform-wide blocking as a normal tool. India's own blocking framework — Section 69A read together with the 2009 Blocking Rules — already gives MeitY channel- and URL-level powers, and the 1,300-URL episode shows the real fix needed is faster compliance and enforcement against non-cooperating platforms, not a broader definition of what counts as blockable "information." Courts reviewing emergency blocks should require the government to show specifically why URL- and channel-level enforcement failed, with a public, time-limited record, rather than accepting platform architecture arguments as a general substitute for that showing. The NEET-UG re-exam went ahead as scheduled and Telegram is back online; the harder question — how far "information" now stretches under Section 69A — is the one the ruling leaves for the next platform this precedent is invoked against.