India Tells Court Telegram Couldn't Detect Exam-Leak Channels Before Block

India's government is defending its block of Telegram in the Delhi High Court with a fairly damning claim: the platform itself admitted it had no way to proactively find channels selling leaked exam papers.

The filing says New Delhi gave Telegram roughly two weeks of notice before the block went live. During that window, regulators allege, Telegram conceded its content moderation works on a takedown-on-report basis, not active detection of the kind of public channels where leaked NEET and other exam materials were being hawked.

Telegram disputes the framing. It says it cooperated with takedown requests and that an outright ban is unlawful and disproportionate.

Both things can be true.

In practice, Telegram has never run the kind of content classification pipeline that Meta or YouTube operate at scale. Public channels with tens of thousands of subscribers are crawlable, but the platform has historically declined to treat that as an obligation. The failure mode here is the one moderation teams know well: reactive takedowns work fine for one bad post, and fail completely when the abuse is a persistent marketplace with a new channel spun up every time the old one dies.

The legal question in Delhi is narrower. Under India's IT Act and the 2021 intermediary rules, platforms keep safe-harbor protection only if they act on government and court orders within defined windows and appoint local compliance officers. The government's argument is essentially that Telegram's self-described inability to detect the channels proactively put it outside that safe harbor once it had been put on notice. Telegram's counter is that it did act on specific URLs it was given.

Which gets to the operational gap nobody wants to say out loud. Regulators want platforms to behave like they have a Trust and Safety org the size of Google's. Telegram has built a product on the explicit promise that it does not. When a government decides that gap is no longer acceptable, the lever it reaches for is network-level blocking at the ISPs, because that is the only lever it actually has.

Worth watching: whether the court accepts the two-week notice as procedurally sufficient, and whether it forces the government to publish the underlying blocking order. India's Section 69A orders are routinely kept confidential, which has been a sore point in prior platform cases including the X litigation in Karnataka.

For security and abuse teams at other messaging platforms, the read is straightforward. If your moderation story is "users can report," expect that to stop being a sufficient answer in jurisdictions where exam fraud, CSAM, or election content gets political attention. Reactive-only doesn't survive contact with a regulator who has been embarrassed in the press.

Operational takeaway: a takedown SLA is not a detection strategy, and courts are starting to notice the difference.