The **Indian government** has informed the **Delhi High Court** that **Telegram** was issued a warning approximately two weeks prior to the platform's nationwide block. Authorities stated that **Telegram** conceded its inability to proactively detect channels involved in selling leaked exam papers. This extensive block, implemented in anticipation of a national medical entrance examination, inadvertently impacted **Telegram** users globally, with disruptions reported as far as the **UAE**. **Telegram** maintains that it cooperated fully with Indian authorities and contends that the imposed ban is unlawful. ## Government's Stance Detailed in Affidavit According to **ANI**, the **Centre** filed its affidavit on June 18. The document outlines that India's **Ministry of Electronics and Information Technology** received numerous complaints regarding **Telegram's** alleged use in the leak of the **NEET-UG 2026** exam, India's national medical entrance examination. The **National Testing Agency (NTA)** identified various channels, groups, and bots circulating leaked materials and engaging in related fraudulent activities. The government clarified that it did not immediately implement an outright block of the application. Initial concerns were directly communicated to **Telegram**. The affidavit states that **Telegram** acknowledged its limited capacity for proactive content detection and confirmed that its moderators were addressing reported channels. <blockquote class="twitter-tweet" lang="en" dir="ltr"><p>The affidavit states that authorities initially adopted the least restrictive measure and did not immediately block Telegram. Instead, officials called Telegram representatives for a meeting on June 3, 2026. During the meeting, the Government raised concerns that Telegram was…</p>&mdash; ANI (@ANI) </blockquote> Hours later, **ANI** reported on **Telegram's** legal challenge against the ban in the **Delhi High Court**. The block remains in effect pending the court's ruling. ## Unpacking the Global Impact and Technicalities Previously, it was reported that India's block had extended beyond its borders, affecting **Telegram** access in regions like the **UAE** due to a **BGP route leak**. **Telegram** CEO **Pavel Durov** challenged the block in court, attributing the issue to Indian telecom **Reliance** and suggesting it was linked to competition with **WhatsApp**. However, network researchers offered an alternative perspective, interpreting the incident as a domestic block that was misconfigured into a global leak. They noted that the autonomous system cited by **Durov** belongs to the insolvent **Reliance Communications**, not the **Meta**-backed **Reliance Jio**. **Reliance Jio** has since publicly refuted **Durov's** claims. In a statement on X (formerly Twitter), the company explicitly rejected any involvement: <blockquote class="twitter-tweet" lang="en" dir="ltr"><p>Recent posts on X have led to speculation regarding Reliance Jio Infocomm Limited (AS55836) and a BGP route misconfiguration. We categorically clarify that Jio has not been involved in any such incident. Jio continues to operate its network in accordance with global Internet…</p>&mdash; Reliance Jio (@reliancejio) </blockquote> The **NEET-UG** re-examination is scheduled for June 21, with the block slated to be lifted on June 22, unless the court's reserved ruling dictates otherwise. Users affected by the disruption can still access **Telegram** via its built-in **MTProto proxy**, as detailed in previous reports.