India enforced a Telegram restriction until June 22 after the service facilitated distribution of leaked examination content.

Telegram head Pavel Durov claims Indian operator Reliance employed BGP hijacking to implement the restriction, affecting connectivity for individuals in locations such as the UAE.

Internet Freedom Foundation labels the prohibition excessive and inconsistent with constitutional standards in addressing exam misconduct.

Restriction Details and Routing Consequences

On June 16 the Ministry of Electronics and Information Technology applied Section 69A of the IT Act to limit Telegram access across India until June 22 based on input from the National Testing Agency. An additional directive requires Telegram to suspend message editing capabilities in India through June 30.

Telegram has petitioned the Delhi High Court against the restriction with an expedited hearing scheduled.

The effects extended past Indian territory.

Durov stated on X that Reliance engaged in sabotage of Telegram connectivity for users abroad including the UAE by means of BGP hijacking.

He described the interference as intentional given lack of response to reports and possible competitive motives tied to Reliance connections with Meta while urging operators to discard unauthorized BGP announcements from AS18101.

Border Gateway Protocol manages internet routing between networks.

BGP hijacking occurs when a network falsely claims IP ranges leading to redirection or interruption of traffic.

Routing records indicate AS18101 started announcing Telegram prefixes coinciding with the domestic restriction explaining external access loss.

The routing issue itself stands confirmed.

Doug Madory of Kentik verified the hijack by AS18101 noting RPKI validation contained wider spread.

Researcher Anurag Bhatia confirmed via public data.

Policy analyst Pranesh Prakash detailed how the route propagated through FLAG Telecom due to failure to filter an invalid announcement reaching users in the UAE.

Analysts question Durov's assertion of deliberate action.

Prakash viewed intentional interference as improbable attributing it to a domestic block that leaked globally.

Madory and Bhatia drew parallels to prior incidents like Iraq's 2023 restriction.

The rivalry aspect remains unclear as AS18101 ties to Reliance Communications rather than Jio though asset overlaps exist.

The anomaly is clear but intent and originator stay undetermined.

Reasons Behind India's Action

The catalyst involves the NEET medical entrance exam taken by millions.

Papers reportedly leaked via paid channels and coaching networks in Rajasthan prompting cancellation and rescheduling for June 21.

The CBI assumed investigation leading to arrests of experts and coaching personnel.

NTA attributed misuse to Telegram channels and bots for selling materials with administrators exploiting edits to falsify timestamps justifying the editing limit.

The agency termed the ban a final measure after targeted removals proved insufficient.

Durov countered that Telegram already eliminated numerous offending channels and the ban overlooks internal sources of leaks.

Political figures like Karti Chidambaram questioned the effectiveness while Telegram highlighted the overreach with analogies to broader closures.

Issues with Platform Blocks

IFF criticizes both procedure and practicality arguing the action exceeds Section 69A authority and fails proportionality for impacting over 150 million users due to limited fraud.

Opacity compounds concerns as blocking orders lack public justification and blocked site lists remain undisclosed.

Examples include long standing inaccessibility of certain outlets without explanation.

Telegram stands out due to its user base drawing attention.

Collateral Effects

Students face the greatest disruption despite protective intent.

NEET candidates depended on Telegram for study resources videos and groups unavailable elsewhere at similar convenience.

Accounts describe lost access to paid legitimate materials forcing reliance on questionable alternatives underscoring misplaced impact on honest users.

Bypassing the Restriction

Telegram includes built in proxy support via MTProto to handle such blocks.

It obfuscates traffic through an intermediary masking direct connections from ISPs.

Encryption persists end to end with proxies unable to access content though IP visibility exists.

Affected users in India or UAE can configure a functional MTProto proxy for restored access without full VPN reliance.

Public lists provide options such as those from StormyCloud or SoliSpirit on GitHub updated regularly.

Users must select trusted sources to avoid logging risks and consider adding VPN layers for enhanced protection.

MTProto Proxy Configuration on Desktop

1. Access Settings then Advanced.

2. Select Connection type under Data and storage.

3. Choose custom proxy and add new entry.

4. Input server port and secret details from the source to activate routing.

On mobile navigate via Settings to Data and Storage then Proxy options add MTProto and enter matching details.

The restriction lifts June 22 post re exam with editing limits to June 30. Court proceedings or unwinding may shorten timelines while external effects could self resolve.

Impacted users regain entry through reliable MTProto proxies chosen carefully.