Delhi High Court backs Telegram block: a test of how India governs its platforms

On 19 June 2026, a division bench of the Delhi High Court refused to lift the Indian government's eight-month block on Telegram, concluding that the Ministry of Electronics and Information Technology had picked the "least restrictive measure" available to stop the encrypted messaging service from being used to distribute leaked exam papers. The bench was responding to Telegram's challenge of a series of blocking orders issued under Section 69A of the Information Technology Act, orders that have also ensnared the Wayback Machine and a string of VPN services since the NEET-UG medical entrance examination paper was compromised in June 2024. Deutsche Welle reported on 19 June 2026 that the case has become "the most high-profile tussle between a tech giant and the Indian government this year," framing the dispute as a stress test of how the world's most populous country will govern its platforms once they reach a critical mass of users. Scroll.in and The Indian Express ran the same ruling on the same morning, with the latter highlighting the court's "least intrusive measure" formulation as the key doctrinal anchor.

The judgment matters beyond the immediate NEET controversy. New Delhi is not merely punishing Telegram for a specific 2024 leak; it is setting a template for how India treats encrypted services that refuse to hand over user data on demand. Telegram's own design — phone-number identifiers, optional end-to-end encryption only in "Secret Chats," and a corporate structure headquartered in Dubai but with no meaningful local presence — has given the ministry an unusually clean target. The court's acceptance of the "least restrictive measure" test suggests that, where platforms refuse to nominate a grievance officer, disclose Indian user data, or hand over decryption keys, blanket blocking will increasingly be treated as proportionate rather than punitive.

The narrow ruling — and what is actually inside it

The bench's order was tight, not sweeping. It refused to quash the specific blocking directions issued by MeitY against Telegram's public channels and mirrors, but it did not foreclose future challenges on different facts. The Indian Express reported that the court accepted the government's argument that Telegram had failed to comply with repeated requests to share information about accounts alleged to have circulated the NEET-UG paper, and that the only remaining remedy under Section 69A was to block the service at the ISP level. The court also noted that the ministry had considered, and rejected, narrower measures — including the takedown of specific channels — on the ground that Telegram's compliance posture made them unworkable. Scroll.in's dispatch framed the result as a procedural endorsement: the Centre, the court said, "followed procedure" in arriving at the block.

The doctrinal pivot is the proportionality test. Indian courts have spent two decades importing the European "margin of appreciation" vocabulary into Article 19 jurisprudence, but they have rarely had to apply it to encrypted services. The Delhi High Court's acceptance of "least restrictive measure" is significant because it imports a frame familiar from U.S. First Amendment intermediate-scrutiny analysis without explicitly borrowing the doctrine. The implication: where the state can show it tried a less intrusive remedy first and was frustrated by the platform's non-compliance, blocking the platform itself becomes the default rather than the last resort.

This is a procedural win for MeitY, which has spent the better part of two years pushing platforms to nominate India-based grievance officers, remove content within 72 hours of a court or government order, and — in the most contested cases — hand over decrypted user data. Telegram, by contrast, has refused to put a legal entity on the ground in India, declined to share user data outside what its public API exposes, and argued in court that its end-to-end-encrypted "Secret Chats" make the demanded disclosures technically impossible. The court's ruling signals that non-compliance is no longer a defence — it is an aggravating factor.

What Telegram argued, and why it lost

Telegram's case in the Delhi High Court rested on three pillars: that the blocking orders were disproportionate, that they violated the platform's right to carry speech under Article 19(1)(a), and that the underlying information demands were technically impossible to satisfy because of the service's encryption architecture. Counsel argued that Section 69A orders must be the last resort, that less intrusive alternatives existed, and that a blanket block punished millions of legitimate users for the actions of a handful of alleged leakers.

None of these arguments carried the bench. The court treated the proportionality question as a function of compliance rather than capability: because Telegram had not appointed a grievance officer or otherwise engaged with the Indian process, the ministry had no realistic alternative to a service-level block. The encryption argument was set aside as beside the point — the government had not asked Telegram to break end-to-end encryption, only to share identifying information on flagged accounts. The court treated that as a routine compliance request, not a backdoor demand.

The result is a quiet but consequential rebalancing of who bears the cost of platform non-compliance. Where a platform engages with the Indian process — as Meta, Google and X have, to varying degrees — narrow takedowns and disclosure orders become the working tools. Where a platform refuses to engage, the platform itself becomes the unit of action. Telegram has now demonstrated the limit of that strategy.

What this means for India's wider platform stack

The Telegram ruling sits inside a stack of similar moves. Since the NEET-UG paper leak in June 2024, MeitY has used Section 69A to block the Wayback Machine, several VPN providers, and a long list of Telegram channels and mirrors. The IT Rules, 2021 already require significant social media intermediaries to appoint Indian grievance officers, enable traceability of "first originator" messages in specified cases, and remove content within tight timelines. The 2023 Digital Personal Data Protection Act added a consent-and-purpose framework that has not yet been operationalised through rules but is widely read as preparing the ground for more aggressive disclosure demands.

What the Telegram ruling adds is judicial confirmation that block-on-non-compliance is a proportionate response. Read narrowly, it applies to encrypted services that refuse to nominate grievance officers and that are credibly linked to specific harms. Read broadly — and this is how Delhi's digital-rights community is already reading it — it gives MeitY a template for treating any platform's refusal to share data as itself a justification for service-level blocking. That is a meaningful expansion of the Indian state's toolkit, and one that will face its next tests in challenges to the blocking of VPNs and to the still-unwritten Digital Personal Data Protection Rules.

Stakes — for Telegram, for India, for the global model

The immediate losers are Indian Telegram users, who since 2024 have relied on VPNs and on-again, off-again access to keep using the service. They are also the diffuse, low-salience losers — the kind the bench's proportionality analysis is built to discount in favour of named, verifiable state interests. Telegram itself loses its largest single market outside the former Soviet Union: India accounted for roughly a third of its global monthly active users at its peak, and the block has already pushed a meaningful share of that base onto WhatsApp, Signal, and X.

The state wins the ability to treat platform non-compliance as an independent ground for blocking. Indian civil-society groups — Internet Freedom Foundation, Software Freedom Law Center, Digital Rights Foundation — argue that this is a slide toward permissioned infrastructure. The government responds, with some force, that it is merely applying existing law to platforms that have chosen not to comply with it. Both characterisations are defensible. The harder question is what happens when the next platform to refuse Indian demands is not a Dubai-headquartered encrypted messenger but a U.S. hyperscaler that India cannot afford to block without economic cost.

For the global conversation, the ruling is a data point in a fast-moving pattern: Vietnam, Pakistan, Türkiye, Russia and Iran have all tightened the screws on encrypted services over the past two years. India has now added a judicial endorsement to its approach, which raises the cost of treating the Indian market as optional. Platforms that want access to a billion-plus users will increasingly need an Indian legal entity, an Indian grievance officer, and a credible plan for compliance with Section 69A and (once finalised) the DPDP Rules. Telegram's loss is the template; the next litigants will be testing how rigid it really is.

What remains uncertain

The judgment is short and the bench has left several questions open. It has not ruled on whether the Section 69A orders themselves are valid on their merits — only that the Centre followed procedure in arriving at them. It has not addressed the encryption architecture question on the merits, only noted that the government's specific demands did not require breaking end-to-end encryption. It has not signalled how it would treat a future challenge from a platform that had appointed a grievance officer, complied with takedown orders, and still refused a specific data request. And it has not addressed the cumulative effect of stacking Section 69A blocks on top of IT Rules compliance demands — the sort of compound pressure that the Supreme Court has historically scrutinised more carefully than individual High Court benches.

For all those reasons, the Telegram ruling is best read as a procedural doctrine with structural implications, not as the final word on India's platform regime. The next round of litigation — likely to come from VPN providers and from digital-rights groups challenging the broader block stack — will test how narrow the bench really meant "least restrictive measure" to be.

Desk note: Wire coverage of the Delhi High Court ruling converged on three points — the bench's acceptance of "least restrictive measure" reasoning, the procedural endorsement of MeitY's process, and the framing of Telegram's non-compliance as the operative fact. Monexus has treated those three frames as the load-bearing elements of the story, and has held off on broader claims about Indian platform governance until the next round of litigation clarifies how broadly this doctrine will be applied.