On June 19, 2026, a vacation bench of the Delhi High Court presided over by Justice Tejas Karia dismissed Telegram's challenge to the Union Government's nationwide block of its platform. The blocking orders, issued by MeitY on June 16 and June 17 under Section 69A of the Information Technology Act, 2000, were timed to protect the NEET-UG 2026 medical entrance re-examination scheduled for June 21. The block expired at midnight on June 22; Telegram's message-editing feature remains disabled in India until June 30. The case number is Telegram FZ LLV & Anr. v. Union of India & Ors., W.P.(C) 8259/2026.
The emergency measure had a genuine target. Fraud channels with names like "PAPER LEAKED NEET," "Re-NEET 2026," and "Private Mafia" spent weeks exploiting Telegram's message-editing feature to manufacture false evidence of pre-exam paper leaks. The modus operandi was precise: an operator would post an innocuous message before the examination, then edit it after the paper became publicly available to insert the real questions while preserving the original timestamp. That fabricated screenshot was then sold as proof of a live leak. Police in Ahmedabad linked one inter-state gang to eight such channels and approximately ₹15 million in fraudulent transactions. Students and families paid for papers that were not leaked at all — they had been deceived by a timestamp. That harm is real, and any analysis of this ruling must begin by taking it seriously.
Why the Government Argued Architecture, Not Content
MeitY's core contention was not that Telegram allowed bad content but that Telegram's design made targeted enforcement impossible. The platform had tried to cooperate: after an NTA complaint on May 21 and a MeitY-Telegram meeting on June 1, Telegram removed hundreds of URLs and more than 150 bots. Fraud channels re-emerged within minutes through mirror handles and backup accounts. Single channels can reach over 200,000 users simultaneously; individual users can deploy up to 40 automated bots. Cloud-based storage makes content persistent across account takedowns. Username-based operation conceals operator identity — one Rajasthan suspect was arrested using a VPN specifically to evade identification. The Attorney General called Telegram "a Frankenstein's creation": powerful enough for mass harm, structured to frustrate accountability.
Justice Karia accepted this reasoning. The court held that Section 69A's term "information" is broad enough to encompass the application itself — not merely specific content hosted on it — and that blocking the entire platform constituted "the least restrictive measure available in the circumstances." The temporary, event-specific nature of the six-day order was treated as central to the proportionality finding.
The Precedent Outlasts the Block
The six-day block is over. The legal reading it produced is not.
Before this ruling, Section 69A was understood to authorize content-specific takedowns — individual URLs, posts, or accounts. Section 79 separately governs intermediary liability, including conditions under which platforms lose safe harbour. These two regimes were deliberately kept distinct by Parliament. The Delhi HC judgment allows blocking power to effectively absorb the intermediary, conflating frameworks Parliament enacted separately. As one constitutional law scholar writing for the Indian Constitutional Law and Philosophy blog observed on June 22, the ruling inverts traditional proportionality doctrine: instead of requiring the state to demonstrate that narrower alternatives were exhausted, the platform's resistance to surgical enforcement becomes the justification for complete removal.
This creates a chilling structural incentive. The more privacy-preserving a platform's architecture — end-to-end encryption, decentralised storage, anonymised identifiers — the less amenable it is to targeted takedowns, and therefore, under this reading, the more proportionate a total shutdown becomes. Applied consistently, the same reasoning could be extended to encrypted email providers, VPNs, or any peer-to-peer network that resists government-directed content removal. Amber Sinha of Tech Policy Press noted on June 22 that the ruling transforms proportionality analysis "from a strict hurdle into a rubber stamp," generating a template future authorities can invoke under any sufficiently charged narrative — public safety, national sovereignty, examination integrity.
Cross-Border Collateral Damage
The block also illustrated why platform-level enforcement is categorically harder to contain than content-level enforcement. Network observers confirmed that AS18101 — registered to the now-insolvent Reliance Communications — began announcing Telegram's IP address prefixes around the time the domestic block took effect. FLAG Telecom (AS15412) failed to filter the misrouted traffic, and the disruption leaked globally, affecting Indian users in the UAE and elsewhere. Telegram CEO Pavel Durov attributed the cross-border outage to deliberate sabotage by Reliance. Technical analysts assessed it as a misconfigured domestic block that leaked through a poorly filtered transit provider, comparing it to similar incidents in Iraq. Jio, a separate entity, issued a clarification distancing itself from the routing error. Whatever the cause, a domestic exam-integrity measure briefly disrupted communication for Indian communities across the Gulf.
What Should Have Been Built Instead
Durov's own post-block statement undermines the efficacy rationale: "The ban has not stopped anything and the leaks simply moved to other apps." WhatsApp groups and Discord servers continued circulating NEET-adjacent fraud content during the block window. The court found the measures proportionate for their stated objective; it did not evaluate whether they achieved it.
The underlying policy gap is not Telegram's architecture — it is India's absence of a dedicated emergency platform-cooperation framework. Section 69A was designed in 2000 and amended in 2008 to block individual pieces of content, not 150-million-user platforms with bot ecosystems. The 2021 IT (Intermediary Guidelines and Digital Media Ethics Code) Rules added grievance-officer and compliance requirements but created no fast-track escalation protocols for time-sensitive national examinations. Pre-agreed response timelines, targeted ISP-level blocks against specific channel IP ranges, real-time hash-matching obligations, and independent judicial sign-off on emergency orders would address exam fraud without requiring a ruling that treats any platform's privacy design as grounds for a nationwide blackout.
India's Supreme Court established in Anuradha Bhasin v. Union of India (2020) that internet access restrictions must meet a necessity-and-proportionality standard. The Delhi HC applied that test, but with wide deference to technical claims the court was not positioned to scrutinise independently. The NEET re-exam needed protection. The fraud channels warranted swift action. What the judgment has produced, however, is a tool calibrated not to the six days it governed but to every future dispute in which a government concludes that a platform's design defeats targeted enforcement.