Can India Switch Off an Entire App to Save One Exam?

On the morning of June 16, lakhs of NEET aspirants across India discovered something stranger than a leaked question paper: their Telegram app had simply stopped working. No warning banner, no graceful wind-down, just a blank loading wheel where a messaging platform used by roughly 150 million Indians used to be. The reason emerged within hours. The Ministry of Electronics and Information Technology, acting on a recommendation from the National Testing Agency, had invoked Section 69A of the Information Technology Act to block the entire platform until June 22, the window bracketing the NEET-UG re-examination scheduled for June 21.

A second order, almost as an afterthought, directed Telegram to disable its message-editing feature for existing messages until June 30, on the theory that students were using edits to backdate "predictions" into proof of leaked papers. By the next afternoon, Telegram's lawyers were inside a vacation bench of the Delhi High Court, calling the shutdown unconstitutional, and the Solicitor General was on his feet promising to show the judges something "shocking." Whatever happens when the matter resumes on June 18, the case has already done something rare: it has turned an obscure provision of cyber law into a live national argument about how much of the internet a government may switch off to protect the integrity of one exam.

The instinct to side with the government here is understandable, and worth taking seriously rather than dismissing. NEET is not a minor inconvenience for a few thousand students; it is the gatekeeper to medical education for over two million candidates a year, and a leaked paper does not just embarrass an agency, it can determine who gets to become a doctor and who does not, on the basis of theft rather than merit. When an exam this consequential has already been cancelled once over leak allegations, regulators are operating under enormous pressure to be seen doing something decisive before the re-test.

Telegram, for its part, has long had a reputation problem in India that predates this episode: its loosely moderated channels, encrypted file-sharing, and refusal to maintain a local office have made it a recurring nuisance in everything from piracy rings to, in 2019, a Kerala High Court petition over child exploitation content. Solicitor General Tushar Mehta leaned on exactly this history when he told the court that the government had been quietly building a case against the platform "since May," and that the material it would eventually produce involved "shocking activities" capable of triggering public unrest around the exam. That is not a frivolous argument. A state that watches organised cheating networks operate in plain sight and does nothing would rightly be criticised too.

But a legitimate goal does not automatically justify any means of achieving it, and this is where the government's order runs into trouble. Section 69A was written, and subsequently interpreted by the Supreme Court in Shreya Singhal v. Union of India, as a tool for blocking specific unlawful content or accounts, accompanied by procedural safeguards under the 2009 Blocking Rules, including a requirement that the affected party be heard before or shortly after the block, under what is commonly called a post-decisional hearing.

What it was never designed to do, and what no precedent in Indian cyber law squarely supports, is shutting an entire communications platform used by 150 million people because some unidentified subset of its users misused it. Telegram's petition makes this point with some force: the company says it took down more than 900 links connected to leaked material as soon as it was notified, deployed its own AI and machine-learning tools to catch violations proactively, and was never given the Rule 8 hearing the law requires before the axe fell. If true, that is not a company stonewalling regulators, that is a company complying and still getting blocked anyway, for the sins of a slice of its user base that the government has not even fully identified yet, by its own admission in court that it still needs to "show individual user IDs."

It is worth sitting with the proportionality question directly, because that is ultimately what the Delhi High Court will be weighing under Article 19(1)(a). Indian constitutional law, going back through the Puttaswamy privacy judgment and the line of free-speech cases that follow it, generally tests restrictions on a four-part scale: is the aim legitimate, is the restriction rationally connected to that aim, is it the least restrictive option available, and does the harm it causes outweigh the benefit it secures. The first prong is easy here; protecting exam integrity is plainly a legitimate state interest. The second prong is shakier, since a platform-wide block does not target the specific channels distributing leaked content any more precisely than turning off the country's electricity grid would target one factory running an illegal furnace.

It is the third prong, necessity, where the government's case looks weakest, because a less restrictive alternative was demonstrably available and, according to Telegram, already in use: notify specific URLs, and the platform removes them within the hour. If targeted takedowns were working well enough that Telegram could point to 900 of them, the case for skipping straight to a total nationwide blackout becomes harder to defend as the only available tool, and starts to look more like an exercise in visible toughness than a calibrated response. As Telegram's own founder Pavel Durov put it in a public post the day before the hearing, the order punishes well over a hundred million ordinary users for the conduct of a comparatively small number of bad actors, who were never going to be the ones inconvenienced by losing access to one app among many.

That last point deserves more attention than it has received, because it cuts against the efficacy argument as much as the fairness one. Cheating networks that are organised enough to obtain and distribute exam papers in advance are, almost by definition, organised enough to switch to Signal, WhatsApp, encrypted email, or a dozen other channels the moment their preferred platform goes dark.

Telegram's lawyers made essentially this argument in court: blocking the entire service does not erase the underlying problem, it just relocates it somewhere harder to monitor, while the cost of the relocation is paid entirely by the millions of legitimate teachers, students, and small businesses who relied on the platform for nothing more sinister than sharing notes and timetables.

There is a useful international parallel here, though it cuts in a more complicated direction than either side's lawyers might like. Brazil's Supreme Court ordered a full nationwide suspension of Telegram in 2022, but for a different reason entirely, the company's repeated refusal to comply with court orders to remove specific accounts and hand over data, not the underlying content itself.

That ban lasted barely 48 hours before it was lifted, once Telegram complied with the outstanding orders. The lesson from Brazil is not that platform-wide bans are unconstitutional everywhere; it is that even courts willing to impose them have treated total suspension as emergency leverage to compel cooperation, not as a routine response to misuse by a subset of users, and have lifted it the moment the narrower compliance problem was solved. India's situation is the reverse:

Telegram says it was already cooperating, which, if the court accepts that framing, makes the leverage rationale unavailable and leaves the ban looking like punishment without a clear administrative off-ramp.

None of this should be read as an argument that platforms get a free pass simply by removing content after the fact, or that exam-leak scandals are someone else's problem to solve. The honest counterpoint to everything above is that NEET has already been cancelled and re-run once this cycle, that public confidence in the exam system is fragile, and that a government facing a re-test in days, with reputational and political stakes attached, cannot always wait for a perfectly tailored remedy to assemble itself in real time.

There is something to that urgency argument, and a court should not pretend emergencies do not compress the time available for fine-grained calibration. But urgency is also precisely the condition under which due process safeguards matter most, not least, because it is exactly when officials are under pressure to act fast that the temptation to reach for the broadest available tool, rather than the most precise one, is strongest.

The 2009 Rules built in a hearing requirement for this reason: not to slow down legitimate enforcement, but to force the state to show its evidence and explain why narrower options will not do, in front of a neutral party, before or very shortly after it switches something off for an entire country. Skipping that step does not make the underlying security concern less real; it just makes the resulting order harder to defend in front of a judge, which is exactly the position the government now finds itself in.

There is also a quieter equality problem buried in Telegram's petition that deserves more attention than it has so far received. The company argues that it has been singled out while "similarly situated intermediaries continue to operate without restriction," a direct invocation of Article 14's equal treatment guarantee. It is true that other messaging and social platforms, including ones with arguably larger Indian user bases, have also hosted leaked-paper rumours and cheating chatter over the years without facing a comparable shutdown.

If the government's real objection is the existence of unmoderated channels distributing exam material, and not something distinctive about Telegram's ownership, architecture, or jurisdictional footprint, then the selective application of the harshest possible remedy to one platform, while leaving functionally similar conduct on competitor apps untouched, starts to look less like content moderation and more like an easy target chosen because Telegram lacks the local lobbying presence, government relationships, and legal infrastructure that bigger competitors have built over the years.

That is a far less flattering explanation for the order than national security, and it is one the government will need to rebut with something more concrete than a list of grievances against Telegram in general, since a five-day inconvenience that becomes a worrying precedent is the real long-term cost here, regardless of how this specific dispute resolves.

Because the precedent is the part that should worry everyone, including people who have no sympathy whatsoever for Telegram as a company. If a full nationwide block survives judicial review on the logic that misuse by an unidentified minority of users justifies switching off a platform for everyone, that logic does not stay confined to exam leaks. The same Section 69A power could, in principle, be invoked the next time a platform hosts coordinated protest organising, viral rumours during a communal flashpoint, or simply content that embarrasses an agency under political pressure to look tough.

None of that requires bad faith on anyone's part; it only requires officials reasonably concluding that what worked once, a fast and total shutdown with a hearing to follow later if at all, is a tool worth reaching for again. Courts exist precisely to draw the line before that becomes a habit, which is why the Delhi High Court's eventual ruling will matter well beyond Telegram's fortunes in India, regardless of how the next NEET retest goes.

Whatever the bench decides, this episode has exposed gaps that outlast the litigation. Exam authorities clearly need security architecture that does not depend on hoping leaked content never reaches a messaging app in the first place, things like randomised question banks generated closer to test time, biometric chain-of-custody for printed papers, and faster forensic tracing of leak sources rather than after-the-fact platform bans.

Lawmakers, meanwhile, have an opening to revisit the blocking rules themselves, perhaps by requiring that any order seeking to suspend an entire platform, as opposed to specific content, clear a higher bar than ordinary takedown requests, with mandatory judicial sign-off and a public statement of reasons rather than a notice that arrives after the lights are already off.

And intermediaries operating in India, Telegram very much included, would do well to treat this as a wake-up call about the cost of operating without a local office, a designated grievance officer, or a visible compliance record that a government can point to when defending cooperation rather than confrontation. Trust, once it has to be litigated in open court, is already in short supply.

What the next few days will decide is not really whether Telegram comes back online by June 22, since it likely will regardless of who wins. What is actually being decided is whether the Indian state's emergency power to silence a platform can be triggered by the misconduct of people it has not yet identified, used against a company that says it was complying, without the hearing the law promises beforehand.

Protecting two million exam aspirants from cheats and protecting a hundred and fifty million ordinary users from being collateral damage in someone else's investigation are both worth fighting for. The measure of a functioning democracy is not which of those goods it chooses when forced to pick one, but whether it has built a legal process precise enough that it rarely has to.