The Ministry of Electronics and Information Technology (MeitY), acting on recommendations of the National Testing Agency (NTA), issued a direction under Section 69A of the Information Technology Act, 2000, restricting access to the Telegram platform in India till June 22, covering the day of the NEET (UG) 2026 re-examination and its immediate aftermath.
New Delhi:The Delhi High Court on Wednesday asked the Centre to file its reply on Telegram’s plea against its order temporarily restricting access to the messaging app ahead of the June 21 NEET-UG 2026 re-examination.
As the matter came up before a vacation bench of Justice Tejas Karia, Telegram’s counsel claimed the curbs were illegal, but Solicitor General (SG) Tushar Mehta defended the government action, saying the platform was being misused and he would reveal “something shocking” tomorrow.
The court adjourned the hearing to Thursday and issued notice to the Centre.
During the hearing, Telegram’s counsel questioned the legality of the government order blocking the platform. He said that over 150 million users had been affected by the Centre’s action on Tuesday.
SG Mehta sought an adjournment, saying that he had not put several things on record.
“If the court posts the matter tomorrow, then there is something shocking I can show…One channel starts, it is prohibited, and then another is started. And with a QR code, you can make a payment. This is continuous,” he said.
“This has not happened overnight. We have been dealing with complaints since May. I don’t wish to go beyond this. This platform is being misused, and imagine the situation which may arise,” Mehta added.
The Ministry of Electronics and Information Technology (MeitY), acting on recommendations of the National Testing Agency (NTA), issued a direction under Section 69A of the Information Technology Act, 2000, restricting access to the Telegram platform in India till June 22, covering the day of the NEET (UG) 2026 re-examination and its immediate aftermath.
A separate direction requires Telegram to disable in India the message-editing feature for already-posted messages till June 30, 2026, addressing the specific structural feature through which the platform has been used to fabricate after-the-event “paper leak” evidence in respect of national examinations, according to an NTA statement.
“Both measures have been taken in the interest of public order, in response to the organised use of the platform by cheating rackets to defraud candidates appearing for the NEET (UG) 2026 re-examination scheduled on 21 June 2026,” the NTA said on Tuesday.
Telegram’s Durov alleges Reliance link to India ban push, Reliance Jio denies involvement
Telegram founder and CEO Pavel Durov on Wednesday alleged that Reliance may have been involved in efforts to ban the messaging platform in India and accused an affiliate of disrupting Telegram’s internet access outside the country – a claim which Reliance Jio denied of having any involvement.
In a post on social media platform X, Durov alleged that Indian telecom operator Reliance was “sabotaging access” to Telegram for millions of users outside India, including in the United Arab Emirates, through a technique known as Border Gateway Protocol (BGP) hijacking.
“The sabotage seems intentional, as Reliance has ignored multiple reports. This may be part of a competitive war, as Reliance is partially owned by Meta, the company behind WhatsApp,” Durov wrote.
He further said he would not be surprised if “Reliance/WhatsApp” were behind lobbying efforts to ban Telegram in India.
“Network operators are advised to reject unauthorised BGP announcements from Reliance (AS18101) to prevent route hijacks and ensure stable Internet access for their users,” he said. “Such abuse of global Internet routing is alarming. I wouldn’t be surprised if Reliance/ WhatsApp were also behind the recent lobbying effort to ban Telegram in India.”
Reliance Jio, in a late evening post, without naming Durov said that recent posts on X have led to speculation regarding Reliance Jio Infocomm Limited (AS55836) and a BGP route misconfiguration.