Telegram FZ LLC v. Union of India (2026): Section 69A empowers blocking an entire platform, not just specific content

When the Ministry of Electronics and Information Technology ordered access to Telegram blocked across India in the days before a high-stakes national examination, the messaging platform went to the Delhi High Court arguing that Section 69A of the Information Technology Act, 2000 does not stretch that far — that the provision permits the blocking of particular information or content, but not the wholesale shuttering of an entire application used by millions. On 19 June 2026, Justice Tejas Karia, sitting on a vacation bench, rejected that argument and dismissed the petition. In doing so, the Court delivered one of the clearest statements yet on the reach of India's principal internet-blocking power: that a platform, in its entirety, can fall within the scope of a Section 69A direction.

The facts in brief

Telegram FZ LLC, the operator of the Telegram messaging service, and a co-petitioner challenged an emergency order issued by the Union government under Section 69A of the IT Act directing that public access to Telegram be blocked. The block was temporary — running in the window around the NEET-UG 2026 re-examination, which was scheduled for 21 June 2026.

The government's stated concern was the integrity of that examination. Following recommendations from the National Testing Agency, the block was framed as a measure to prevent the leak of question papers and to curb organised cheating, with the Court noting that nearly 2.2 million candidates were due to sit the re-examination. The order was thus presented not as a permanent ban on the platform but as a short, time-bound restriction tied to a specific public-interest objective.

Telegram challenged the block by way of W.P.(C) 8259/2026, contending — among other things — that Section 69A did not authorise blocking an entire platform and that the procedure followed in issuing the emergency direction was deficient.

The question

The petition turned on two connected questions. The first was one of statutory reach: does Section 69A of the IT Act — which speaks of issuing directions for "blocking for access by the public" of "any information" — extend to blocking an entire application or platform, or is it confined to discrete items of content, such as specific posts, messages, channels or URLs?

The second was a question of process and proportionality. Even if the power exists, was its exercise here lawful — given that the block was an emergency, interim direction, and given the constitutional demand that any restriction on access to a communications medium be proportionate to the objective it serves?

What the Court held

On the first question, the Court held that the power under Section 69A does reach an entire platform. The reasoning turned on the statutory definition of "information". Justice Karia noted that the expression "information" under Section 2(1)(v) of the IT Act is defined broadly — to include data, text, codes, computer programmes and software, among other things — and concluded that there was no reason to exclude an application or software platform from the ambit of that definition. As the Court put it, the Centre was "empowered under Section 69A to issue directions for blocking public access to Telegram."

The Court also pointed to the architecture of the platform itself as relevant to why a whole-platform block could be a justified response. It observed that Telegram's particular features — public channels capable of holding very large memberships, bots able to disseminate content without human intervention, the concealment of users' phone numbers, and the ability to edit a message without any time limit — made it a potent vehicle for the rapid spread of leaked material and misinformation, the very harm the block was meant to forestall.

On the second question, the Court found the proportionality test satisfied. It identified and applied the familiar four limbs:

The Court held that the necessary requirements of proportionality — a legitimate objective, a rational nexus between that objective and the measure adopted, the necessity of the measure on the facts, and the adoption of the least restrictive option available — had each been met. The legitimate aim was the integrity of an examination affecting millions of candidates; the temporary, time-bound character of the block was central to its being the least restrictive course.

On procedure, the Court accepted that an emergency interim blocking direction may be issued first, with a fuller hearing to follow. It held that, in cases of emergency, an interim direction may be issued upon satisfaction of the conditions under Section 69A, and that a post-decisional hearing can be afforded before the final order confirming or revoking the interim direction — rejecting the contention that exhaustive pre-decisional reasoning must precede every emergency directive. The petition was accordingly dismissed.

Analysis

The doctrinal core of the judgment is the move from "information" to "platform". Section 69A is, on its face, a power to block information; Telegram's argument was that an application is not information but the conduit through which information flows. The Court closed that gap by reading the IT Act's own definition of "information" — which expressly captures codes, computer programmes and software — as wide enough to cover the software platform itself. Once that interpretive step is taken, blocking the application is just a species of blocking information, and the textual objection falls away.

That reasoning has consequences well beyond Telegram. It means the entire-platform block is not a doctrinal anomaly to be reserved for the most extreme cases, but an option that sits squarely within the ordinary scope of Section 69A. The proportionality analysis then does the limiting work: a whole-platform block is lawful where it is the least restrictive effective measure for a legitimate end. Here, the temporariness of the block and the scale of the public interest — an examination involving millions — were what carried the proportionality finding. The implicit corollary is that a permanent or open-ended block, or one imposed where targeted content-blocking would have sufficed, would face a far harder proportionality inquiry.

The procedural holding is also significant. By endorsing emergency interim blocking with a post-decisional hearing to follow, the Court accommodated the practical reality that the harm Section 69A targets — here, the leak of examination material — is often time-critical and cannot wait for an exhaustive prior hearing. This tracks the structure of the Blocking Rules, 2009, which themselves contemplate an emergency procedure. The safeguard, on the Court's reasoning, is not pre-decisional exhaustiveness but the requirement that reasons be recorded and that a hearing follow.

It is worth situating this against the broader Section 69A jurisprudence. The provision and its blocking machinery were upheld, with procedural safeguards read in, in Shreya Singhal v. Union of India (2015) — the same decision that struck down Section 66A. More recently, the scope and procedure of Section 69A and the related compliance regime have been litigated in the X Corp matters before the Karnataka High Court. The Telegram decision is distinct from those: it does not concern the Sahyog portal or Section 79 intermediary obligations, but the specific and narrower proposition that a Section 69A direction can target an application as a whole.

Why it matters

For platforms, the judgment removes a textual line of defence that had some intuitive appeal: the argument that Section 69A reaches only content, never the application itself. After Telegram, that argument is unlikely to succeed in the Delhi High Court — the contest shifts almost entirely to proportionality and process. The practical question for an intermediary facing a whole-platform block becomes whether the block was temporary, whether less drastic measures (such as blocking specific channels or content) could have achieved the same end, and whether the emergency procedure and post-decisional safeguards were observed.

For the government, the decision confirms a powerful tool: in a genuine emergency, and where targeted blocking is impractical against the platform's architecture, the Centre may block an application in its entirety, provided the measure is proportionate and time-bound. For users and for free-speech advocates, the case is a reminder that the principal check on this power is no longer the text of Section 69A but the discipline of proportionality — and that the temporariness of a restriction will often be decisive in whether it survives.

Related on Valkya

• X Corp v. Union of India (Karnataka): Section 69A and the blocking regime
• X Corp v. Union of India: the Sahyog portal and Section 79
• Shreya Singhal v. Union of India: striking down Section 66A
• AGIJ Promotion v. Union of India: stays on the IT Rules 2021

Sources

• LiveLaw, "S.69A IT Act Empowers Centre To Block Entire Intermediary Platform, Not Just Specific Content: Delhi High Court In Telegram Case"
• Bar & Bench, "Social media platforms can be blocked in entirety under Section 69A of IT Act: Delhi HC rules in Telegram case"
• Verdictum, "Delhi High Court Dismisses Telegram Plea Against Temporary Ban"
• Verdictum, "Section 69A IT Act Permits Issuance Of Interim Blocking Directions; Post Decisional Hearing Can Be Afforded Before Final Order: Delhi HC While Upholding Telegram's Ban (2026:DHC:5145)"