The Order, and What It Actually Blocked
On June 16, 2026, India's Ministry of Electronics and Information Technology (MeitY) issued a blocking direction under Section 69A of the Information Technology Act, 2000, ordering ISPs to make Telegram inaccessible nationwide. The trigger, per the National Testing Agency's (NTA) recommendation, was a wave of Telegram channels — operating under names like "PAPER LEAKED NEET" and "Re-NEET 2026" — charging students sums from a few thousand to several lakh rupees for supposedly leaked copies of the NEET-UG medical entrance re-exam, scheduled for June 21 after the original test was scrapped over leak allegations. MeitY separately ordered Telegram to disable message editing for Indian users through June 30 — a 14-day window — saying the feature had been used to fabricate after-the-fact "leak" evidence (TechCrunch; The Quint). The platform came back online on June 23, a full week after it went dark (The Wire).
The Case for the Block
Give the government its due. NEET-UG is the sole admissions gate for every government medical seat in the country; a compromised exam doesn't just embarrass an agency, it hands seats to people who cheated at the expense of students who didn't. The NTA says channel-by-channel takedowns hadn't kept pace with new fraud channels spinning up faster than they could be reported. NTA Director General Abhishek Singh framed the logic plainly: "Even though they can continue operating the channels, if there is no clientele, the fraud will be prevented, and the students will be protected" (TechCrunch). A block confined to the exam window and its immediate aftermath is, on its face, a bounded, sunset-limited intervention rather than an open-ended ban.
Where the Justification Breaks Down
The trouble is that a bounded intervention against a real harm can still set an unbounded precedent, and the precedent is what should worry anyone who cares about proportionate regulation. Section 69A, as the Supreme Court read it in Shreya Singhal v. Union of India (2015), is meant to be a narrow tool: block specific, identified content, on specific grounds, with written reasons behind it. The Telegram order didn't ask ISPs to block particular channels; it switched off the entire application for a user base courts and commentators put at roughly 150 million people, the overwhelming majority of whom had no connection to the leak scam (The Wire). Telegram made the obvious argument to the Delhi High Court, calling the order a product of "complete non-application of mind" that punished the whole service instead of the offending channels. Founder Pavel Durov put it more bluntly on X: the ban "punishes 150M+ ordinary Telegram users in India — not the insiders who leaked the exam materials," adding that the fraud "just moved to other apps" once Telegram went dark.
That last point deserves more weight than it's been given. If the scam relocated within days, as Durov and several outlets reported, the block didn't eliminate the underlying harm — it demonstrated that shutting down one app doesn't fix a leak-vetting problem that lives inside exam security, not inside Telegram's server stack.
What the Court Actually Decided
The Delhi High Court heard Telegram's petition, W.P.(C) 8259/2026, on June 17 and dismissed it on June 19. Justice Tejas Karia found the government had identified a legitimate objective — protecting the integrity of a national exam — and had adopted the least restrictive measure available (Delhi High Court judgment). That finding is defensible if targeted takedowns had genuinely stopped working. But the Internet Freedom Foundation's response to the ruling identifies the deeper problem: Shreya Singhal upheld Section 69A specifically because it was confined to blocking "specific, identified information," not entire intermediaries. Reading that power as reaching a whole platform, IFF argued, "is to treat the speech of a whole population as a single switch to be turned off" (IFF statement). IFF's earlier, pre-ruling demand — publish the MeitY order and the NTA's underlying recommendation, confirm whether Telegram got a hearing, and place the blocking committee's record before any reviewing court — went unmet before the block took effect. That means the "least restrictive measure" finding rests on reasoning the public still can't independently check.
The Real Cost Isn't the Week
A seven-day outage is survivable; Indian users have weathered worse platform disruptions. What's not survivable for the credibility of "narrowly tailored" content regulation is a court-blessed reading of Section 69A that treats an entire messaging app as fair game whenever a subset of its users commit fraud. Extend that logic and any platform hosting 150 million Indians — a WhatsApp, an Instagram, an X — becomes vulnerable to a full shutdown the next time bad actors exploit a feature faster than a regulator can process takedown notices. That is a governance failure mode dressed up as an enforcement success.
The Fix Was Already Available
Nothing here required a blanket ban. The NTA's own record credits coordinated takedowns with containing earlier waves of the same scam; targeted blocking of identified channels, paired with expedited action against the operators behind them, addresses the actual bad actors without degrading a communications tool for 150 million uninvolved users. If MeitY believes platform-wide blocks are sometimes unavoidable, the honest fix is procedural rather than substantive: publish blocking orders and the recommendations behind them as a matter of course, as IFF has asked, so that "proportionality" is something courts and the public can verify — not something they're asked to take on faith.