The holding that an entire platform can be switched off is defensible on the statute's text. What the judgment does not supply is a limiting principle.
On 19 June 2026, the Delhi High Court dismissed Telegram's challenge to the temporary block imposed on the platform ahead of the NEET-UG re-examination. Most of the attention has understandably gone to the block itself: a widely used messaging service with more than 150 million Indian users, made unavailable across India, even if only for a few days, on the eve of a high-stakes examination.
But the more durable consequence of Telegram FZ LLC v. Union of India lies elsewhere. For the first time, and with reasons, an Indian court has held that an entire platform can be blocked under Section 69A of the Information Technology Act, 2000, because the application itself qualifies as “information” within the meaning of the statute.
That holding is defensible on the text. What it does not contain, and what the next case will need, is a principled limit on how far the power reaches.
Understanding the Delhi High Court's Holding: Switching off the Platform
Section 69A empowers the Central Government to direct the blocking of “any information generated, transmitted, received, stored or hosted in any computer resource”, on grounds that mirror the permissible restrictions on speech under Article 19(2) of the Constitution. Telegram's argument was that this is a power to block discrete information, that is, specific content, channels, accounts or files, and not a power to switch off an intermediary in its entirety.
The Court rejected that reading. It turned to the definition of “information” in Section 2(1)(v), which expressly includes “codes, computer programmes, software and databases”, and reasoned that an application, being a compilation of exactly those components, is itself “information” (paragraphs 33 to 37). A narrower construction, it held, confined to individual posts or accounts, would render the provision “otiose” (paragraph 35). On that basis, Respondent No. 1 was held to be “empowered under Section 69A of the IT Act to issue directions for blocking public access to Telegram”.
The Court's judgment is prima facie reasonable and is in no way a leap of logic, given that this reading is available in the plain text of the statute itself. The definition in Section 2(1)(v) does mention software and computer programmes, and the Court did not conduct its legal analysis on the assumption that everything on Telegram was unlawful. Moreover, the block was limited in time to 22nd June 2026 and was primarily based on the conduct of identified fraud networks operating on the platform, rather than on the platform's mere existence itself.
The difficulty does not lie in making such a construction; rather, it lies in the fact that, once adopted, there is no obvious stopping point for platform blocking.
Evolution of Section 69A: A Ladder, Climbed One Rung at a Time
The significance of the Delhi High Court's ruling becomes clearer when understood in the context of the sequential jurisprudential development of Section 69A.
The original and uncontroversial use of Section 69A is to block specific content such as a URL, a post, or a particular item of information. In 2023, this power climbed a rung in the case of X Corp v. Union of India. The Karnataka High Court held that Section 69A's power “is not tweet-specific but extends to user accounts in their entirety”, while dismissing X's challenge with costs of ₹50 lakh. The justification for expanding Section 69A's scope from content blocking to account blocking was grounded in preventive reasoning. In the language of the Karnataka High Court, the State “need not await the arrival of an avalanche of mishaps” and can act in anticipation, since “a surgeon does not wait till gangrene is developed”.
Irrespective of the subject of blocking, the underlying rationale has largely remained consistent over the years: the potential of instantaneous large-scale dissemination, the inadequacy of after-the-fact removal, and the State's approach of prevention being better than the cure. From a post, to an account, to, ultimately, the platform itself, the Telegram ruling serves as the final rung in the ladder of blocking information under Section 69A.
Notably, this is not the first time that entire applications have been blocked under Section 69A. The 2020 blocking of TikTok, PUBG and other applications did precisely that; however, those orders were never tested in a reasoned merits judgment on whether the provision authorises platform-level blocking at all. Telegram appears to be the first decision to supply that reasoning, and marks the moment that the practice acquired a precedent.
Analysis of the Holding: The Missing Limiting Principle
If an application is “information” because it is built of code, software and databases, then the construction draws no line short of every application, browser, operating system or website, each of which is built of the same materials. On this reasoning, what distinguishes Telegram from any other platform is not the statute but the facts of the case.
The Delhi High Court offered two brakes in its judgment. The first is proportionality, which the Court applied and found satisfied. However, proportionality only tests how a power is exercised in a particular set of facts. Its application presupposes that the power under Section 69A extends to the platform; therefore, the proportionality test cannot answer the prior question of whether it should extend to the platform in the first place. The second brake is the temporariness of the order, which limits how long a block may last; in this case, till 22nd June 2026. However, neither brake says anything about when a platform block should be imposed in the first place.
This is not to say that the block was wrong or unjustified in the facts of the present case. The Delhi High Court identified a genuine concern: fraud networks reconstituting themselves via mirror channels and user migration, much faster than channel-by-channel takedown could keep pace with. Notably, all of this is against the backdrop of an examination of national importance, taken by roughly 22 lakh candidates. Faced with that, under acute time pressure, the State had a real and legitimate objective.
The concern is not the outcome in this case. It is that the holding, read as a precedent, travels to the next platform and the next set of facts without a clearly stated limit.
What a Workable Limit Could Look Like: Platform Blocking as Measure of Last Resort
That gap matters because of how Section 69A came to be upheld in the first place. In Shreya Singhal v. Union of India (2015), the Supreme Court sustained the provision precisely because it is “a narrowly drawn provision with several safeguards” (paragraph 109). Blocking is available only where the Central Government is satisfied of its necessity, which must be covered under the grounds of Article 19(2), and reasons must be recorded in writing so that the order can be assailed in a writ petition.
A provision held constitutionally valid on the basis of its narrowness has now been read to reach the broadest possible object, the platform itself. That is not, by itself, impermissible. However, it is the kind of expansion that ordinarily calls for the Court to say, in the same breath, where the new reach stops.
Guidance for a future limit can be drawn from the Telegram judgment itself. The block was temporary and based on a recorded finding that content and account-level measures had been tried and failed against Telegram's architecture. Those features point towards the test the doctrine now needs. Platform blocks should be treated as a measure of last resort.
They should be permitted only on the basis of a recorded and reviewable finding that narrower interventions are demonstrably unworkable in the specific circumstances, while ensuring that the blocks are time-limited and subject to built-in review. Such a standard would keep the power available for rare and genuine cases, such as the circumstances the State faced this time, while ensuring that the next platform-blocking order is tested against a limiting principle rather than merely the elasticity of the word “information” in the provision's text.
The Future of Online Speech Regulation in India
The Delhi High Court's Telegram ruling arrives as the larger contest over online speech regulation in Indian courts remains unresolved. In X Corp v. Union of India (2025), the Karnataka High Court upheld the Sahyog content-takedown architecture while holding that Article 19 is “a charter of rights conferred upon citizens only”, and therefore a foreign platform cannot invoke it. With the platform itself unable to claim the right, and its users not before the court, the question of when an entire platform may be blocked becomes harder to test.
This is precisely why the limiting principle matters even more. Section 69A's ladder has developed rung by rung, finally reaching the platform itself. When the question of platform blocking reaches the Supreme Court, irrespective of the facts of that case, the Apex Court will need to supply what the Telegram ruling left unstated: not whether the power can extend to a platform, but the principle that determines when it should.
Author is a Law Clerk-cum-Research Associate at Supreme Court of India. Views are personal.