The Delhi High Court in Telegram FZ LLC & Anr. v. Union of India & Ors.[1], through its judgment dated June 19, 2026, held that Section 69A of the Information Technology Act, 2000 (“IT Act“) empowers the Government to block an entire intermediary platform, and not merely specific pieces of unlawful content. The Court dismissed Telegram’s challenge to the Government’s order blocking the platform across India in the run-up to the NEET UG, 2026 re-examination.
Background
The dispute arose out of the misuse of Telegram by third parties to circulate fake NEET UG, 2026 examination papers and misleading information. The National Testing Agency first flagged this misuse to the Ministry of Electronics and Information Technology (“MeitY“) on May 21, 2026. A meeting followed on June 3, 2026, at which Telegram’s content moderation framework was discussed, though the parties later disputed what exactly was said, with Telegram contesting the Minutes of Meeting issued by MeitY. MeitY subsequently shared a list of 1,300 (one thousand three hundred) URLs linked to fraudulent NEET activity, of which Telegram disabled 900 (nine hundred).
On June 16, 2026, MeitY passed an interim order under Section 69A of the IT Act that Telegram and its associated URLs be blocked till June 22, 2026, and that the message editing feature be disabled till June 30, 2026, citing the risk of backdating scams where edited messages could be used to fabricate proof of a leak. After a hearing on June 17, 2026, the Committee under Rule 7 of the Information Technology (Procedure and Safeguards for Blocking for Access of Information by Public) Rules, 2009 (“2009 Rules“), unanimously confirmed the interim direction, and the Secretary passed a final order to that effect on June 18, 2026.
Key Issues and Petitioners’ Arguments
Telegram challenged both orders primarily on two grounds. First, that the orders were vitiated by non-application of mind, since the interim order merely recited statutory language without independent reasoning, and the requisite satisfaction for confirmation lay with the Committee rather than the Secretary as contemplated under Rule 9(4) of the 2009 Rules. Telegram also argued that a platform-wide block was disproportionate and ultra vires Section 69A of the IT Act, which Telegram argued empowers blocking of specific ‘information’ and not an entire intermediary. Telegram relied heavily on Anuradha Bhasin v. Union of India[2] for the proposition that only the least restrictive measure may be adopted, and on Bishamber Dayal Chandra Mohan v. State of U.P.[3] on the reasonableness of restrictions on fundamental rights.
Court’s Analysis and Findings
Non-Application of Mind
The Court held that, given the emergency nature of the interim order, the reasons recorded were sufficient and disclosed a direct nexus between the material considered and the conclusion reached. The Court further rejected the argument that the final order could not supplement the interim order’s reasoning, holding that the statutory scheme of Section 69A of the IT Act read with the 2009 Rules expressly contemplates an interim direction based on the Secretary’s satisfaction, followed by a post decisional hearing and a final order confirming or revoking it. Compliance with individual takedown requests was also held to be immaterial to the validity of the platform level direction, since the two operate under different rules altogether.
Scope of Section 69A
On whether Section 69A of the IT Act permits blocking an entire platform, the Court accepted the Centre’s submission that ‘information’ under Section 2(1)(v) of the IT Act is defined broadly to include codes, computer programmes, software and databases, and that an application or platform, being a compilation of these, falls within that definition. The Court therefore held that MeitY was empowered to block Telegram in its entirety, and not merely specific URLs or channels.
Proportionality
Applying the four part test from Anuradha Bhasin (legitimate goal, rational nexus, necessity, and least restrictive measure), the Court found that each limb of the test was satisfied in the present case. It placed significant weight on Telegram’s technical architecture, including its cloud based infrastructure, automated bot ecosystem, and capacity for instant creation of mirror or backup channels, which the Court found had rendered channel specific takedowns ineffective, since removed content and audiences simply resurfaced elsewhere. The message editing feature was similarly found capable of enabling backdated proof of a leak, a risk Telegram’s own CEO had publicly acknowledged while promising a more visible edited label. Crucially, the Court emphasised that both restrictions were tightly time bound, one until June 22, 2026 and the other until June 30, 2026, coinciding with the examination window, which demonstrated a narrowly tailored measure rather than an open ended prohibition. Accordingly, proportionality was accordingly answered in the Centre’s favour, and the petition was dismissed.
Conclusion
This judgment meaningfully expands the Government’s blocking powers under Section 69A of the IT Act, confirming that the provision is not confined to discrete pieces of content but extends to an intermediary’s platform as a whole where its architecture is shown to defeat narrower enforcement. At the same time, the outcome was closely tied to the temporary and the event specific nature of the restriction. For intermediaries operating in India, the judgment is a reminder that documented, repeated engagement with regulators, however cooperative, will not by itself insulate a platform from platform-wide action if the underlying architecture keeps enabling the harm sought to be prevented.
[1] W.P.(C) 8259/2026 & CM APPL. 39036/2026.
[2] (2020) 3 SCC 637.
[3] (1982) 1 SCC 39.
English
Chinese (Simplified)
Japanese