Case: Telegram FZ LLC & Anr. vs. Union of India & Ors., W.P.(C) 8259/2026 & CM APPL. 39036/2026
Court: Delhi High Court | Coram: Hon’ble Mr. Justice Tejas Karia, Vacation Judge
Decided: 19 June 2026
On 19 June 2026, the Delhi High Court dismissed Telegram’s writ petition challenging a government order that blocked the platform nationwide, affecting more than 150 million Indian users. The ruling is significant not because platform blocking itself is new — India has used Section 69A of the Information Technology Act, 2000 before — but because of what was blocked and why the Court said it was lawful. For the first time, a court has held that Section 69A’s power to block “information” extends to an entire application, not merely to specific posts, channels, or accounts. For lawyers, law students, and anyone tracking the boundaries of platform regulation in India, this case deserves a close read.
How a Paper Leak Took Down an App
The dispute traces back to a fraud ecosystem operating on Telegram around the NEET UG 2026 medical entrance examination. Channels with names like “PAPER LEAKED NEET” and “NEET Mafia” were openly demanding money from anxious candidates in exchange for supposedly leaked question papers. The problem wasn’t an isolated bad actor — when one channel was taken down, mirror channels reappeared almost as quickly.
The timeline matters for understanding the Court’s eventual finding that the government did not act on a whim:
21 May 2026 — The National Testing Agency (NTA) alerted the Ministry of Electronics and IT (MeitY) that Telegram bots and channels were selling fake NEET papers.
1–5 June 2026 — A MeitY meeting was held with Telegram. The company disputed the official minutes of that meeting but did take down 900 of the 1,300 flagged URLs.
16 June 2026 — An interim order blocked the platform within one hour and disabled its message-editing feature.
17–18 June 2026 — A Rule 7 Committee hearing was held, culminating in a Final Order confirming the block.
19 June 2026 — The Delhi High Court dismissed Telegram’s writ petition.
21 June 2026 — The NEET re-examination was conducted for roughly 2.2 million candidates.
What the Government Actually Ordered
The Impugned Order, issued on 16 June 2026, did four distinct things: it blocked Telegram and its associated URLs across India until 22 June 2026 (the original exam date); it suspended the app’s editing feature until 30 June 2026, specifically to prevent users from fabricating backdated “proof” that a leak had occurred before the exam; it directed the Department of Telecommunications to instruct ISPs and app stores to enforce the block nationwide; and it referred the matter to the statutory Rule 7 Committee within 48 hours, as required for review of urgent blocking directions.
The government’s legal basis was Section 69A of the IT Act, invoked on the grounds of public order and the prevention of incitement to a cognizable offence — with the scale of the case (2.2 million exam candidates and 150 million platform users) looming over every subsequent argument.
Two Issues Before the Court
Telegram’s challenge ultimately turned on two questions. First, was the order vitiated by non-application of mind — did MeitY simply recite the language of Section 69A without independently assessing the material before it? Second, did a platform-wide block, even a temporary one, satisfy the constitutional requirement of proportionality given its impact on a vast and largely innocent user base?
Telegram’s Case: A Sledgehammer for a Scalpel Problem
Appearing for the petitioner, Senior Advocate Mr. Dhruv Mehta built a six-pronged argument. The order, he contended, did little more than reproduce statutory language without conducting any independent proportionality assessment specific to a platform-wide block. Telegram pointed to its own conduct as evidence of good faith — it had been engaging with authorities since 20 May, had disabled the majority of flagged URLs, and operated AI/ML moderation alongside hash detection and human review.
The constitutional core of the argument rested on Anuradha Bhasin v. Union of India, (2020) 3 SCC 637, which Telegram read as requiring the government to target specific channels or posts rather than banning an entire application — the least restrictive means available. Relatedly, Telegram argued the order was ultra vires Section 69A altogether, since the provision empowers the blocking of specific “information,” not a blanket ban on an intermediary platform as a whole.
Two further points rounded out the petition: a procedural objection that Rule 9(4) of the 2009 Blocking Rules requires the Secretary, not the Committee, to independently apply his mind, and a substantive objection that 150 million users — including students relying on Telegram for legitimate study material — were being disproportionately punished for the conduct of a relatively small number of bad actors.
The Government’s Case: An Architecture That Defeats Takedowns
For the Union of India, Solicitor General Mr. Tushar Mehta, Attorney General Mr. R. Venkatramani, and Additional Solicitor General Mr. Chetan Sharma argued that channel-by-channel enforcement was structurally futile. Mirror channels, bots, and anonymous usernames allowed operators to reconstitute almost instantly after every takedown, making piecemeal action an exercise in chasing shadows.
The government placed particular weight on the editing feature: message-editing combined with timestamp retention allowed bad actors to fabricate “leaked” chat artefacts designed to appear as though they predated the exam. This, the government argued, was not a hypothetical risk but an active fraud mechanism that the platform’s own design enabled. The Centre also pointed to a longer history of frustration — more than 35 prior engagements with Telegram since October 2024 — and argued misuse had only intensified as the re-exam date approached.
On the statutory question, the government leaned on Section 2(1)(v) of the IT Act, which defines “information” to include codes, software, and databases. An application, the argument went, is itself an aggregation of such information, bringing it squarely within Section 69A’s reach. The government also invoked broader public-order concerns, citing I4C reports linking Telegram to CSAM, malware, and cyber-fraud, along with multi-state arrests connected to a fraud operation exceeding ₹1.5 crore. Finally, the government pointed to public statements made by Telegram’s own CEO as corroborating, rather than undermining, its case.
The Tweet That Backfired
One piece of evidence did unusual work in this case. On 16 June 2026, Telegram CEO Pavel Durov posted that the company had removed “hundreds of channels sharing leaked exam materials,” that it was making the “edited” label more visible to prevent “backdating scams,” and that banning the platform — even temporarily — was a mistake.
The Final Order devoted an entire section to this statement, and for good reason. Read against Telegram’s defence, the tweet cut several ways at once: it confirmed that channels existed at the scale the NTA had alleged; it conceded that Telegram’s moderation was reactive removal rather than preventive screening; it used the phrase “backdating scams” without disputing that the phenomenon existed; and it implicitly admitted that the platform’s existing “edited” label had been inadequate. The Committee treated this as a voluntary admission that the platform’s safeguards reflected a deliberate policy choice rather than a technical limitation — a framing that significantly weakened Telegram’s “we did all we reasonably could” defence. It is a useful reminder, for counsel advising any platform client, that public statements made for PR purposes can become evidentiary admissions in litigation.
Issue 1: Non-Application of Mind, Rejected
The Court held that the Impugned Order traced a clear evidentiary chain — from the NTA’s original complaint, through the 3 June meeting, the disputed compliance record, and the specific apprehension around the editing feature — and that this amounted to more than a mechanical recital of Section 69A. Given the emergency, time-critical nature of an interim direction under Section 69A, the Court held that the reasons supplied at that stage were sufficient, and that natural justice was satisfied through the post-decisional hearing rather than requiring a pre-decisional one.
Importantly, the Court read the two-stage structure under Rule 9 — interim satisfaction by the Secretary, followed by a Rule 7 Committee hearing and a detailed Final Order — as exactly what the 2009 Rules contemplate, rather than an impermissible attempt to retroactively supplement a thin interim order. The Final Order’s thirteen-section reasoning, drawing on NTA and I4C reports, platform architecture, and Durov’s own statement, further fortified the nexus between the material before the government and its conclusion.
Issue 2: Proportionality, Applied
On proportionality, the Court applied the four-part framework from Anuradha Bhasin: legitimate aim, rational nexus, necessity, and least restrictive measure. It found a legitimate aim in protecting the integrity of a sovereign examination affecting 2.2 million candidates and in preventing a public-order breakdown. The rational nexus prong was satisfied because mirror channels, bots, anonymity, and message-editing were not hypothetical risks but mechanisms actually exploited by bad actors. On necessity, the Court accepted the government’s account that entity-by-entity takedowns had been attempted for weeks without success, with channels demonstrably reappearing. And on the least restrictive measure, the Court emphasised the narrow time-bounding of the order — the platform block ran only until the original exam date of 22 June, and the editing suspension only until 30 June.
The Court’s own words capture the conclusion: the measures adopted constituted the least restrictive means of achieving the stated objective, and the action could not be held disproportionate.
Can Section 69A Block an Entire Platform?
The case’s most consequential holding is interpretive. Telegram urged a narrow reading of “information” under Section 69A — specific posts, files, messages, or accounts, not the software platform itself — arguing that blocking an entire app to address unlawful content on it was using a sledgehammer where a scalpel was required, and that doing so exceeded what the statute intended.
The Court rejected this reading. Section 2(1)(v) of the IT Act expressly defines “information” to include codes, computer programmes, software, and databases — not merely messages or files. An application, the Court reasoned, is itself a compilation of code, databases, and APIs, and is therefore an aggregation of “information” within the meaning of the Act. On this reading, the power under Section 69A validly extends to the platform itself, not just to discrete content hosted on it.
The Verdict
The writ petition was dismissed. Both the Interim Order of 16 June 2026 and the Final Order of 18 June 2026 were upheld as lawful and proportionate. The Court found no non-application of mind, holding that the reasons in the order — fortified by the Final Order’s detailed findings — were sufficient. It found the proportionality test satisfied, treating the time-bound, event-linked nature of the block as the least restrictive effective measure available. And it held, as a matter of statutory construction, that Section 69A’s reference to “information” is broad enough to cover an application or platform in its entirety.
Why This Judgment Matters
For practitioners, the ruling does real work in three directions. On the scope of Section 69A, it is the first clear precedent holding that “information” can extend to an entire app or platform, which strengthens the government’s hand in platform-level — rather than merely content-level — blocking, and will be relevant to how intermediary-liability and takedown notices are drafted going forward.
On proportionality, the case reshapes how repeated, demonstrated architectural failure is treated: rather than weakening the government’s position, a documented pattern of takedowns being defeated by platform design can actually satisfy, rather than defeat, the proportionality requirement. The judgment also draws a meaningful line between Anuradha Bhasin’s internet-shutdown context and app-specific blocking, signalling that time-bound, event-linked orders are likely to be the key to surviving judicial review in future cases of this kind.
For anyone advising intermediaries on compliance with the 2021 IT Rules, the case is a useful precedent — and a cautionary tale. It is also a reminder, worth repeating to any corporate client, that public statements from a CEO or spokesperson are not free of legal consequence; they can become evidentiary admissions in litigation long after the press cycle has moved on.
This analysis is based on the case summary as presented and is intended for general informational and educational purposes. It does not constitute legal advice. Readers should consult the full text of the judgment and qualified counsel before relying on this case for any matter.
