Telegram blocked in India till June 22 for NEET

  • Thread starter Thread starter Sushubh
  • Start date Start date
  • Featured
  • Replies Replies 58
  • Views Views 721
First they banned Porn (Anyone who raises question would be called pervert. probably)
then they banned torrent sites (Anyone who raises questions would be told "You wouldn't download a car")
then they started VPN logging policies (Anyone who raises question would be slammed with "Matter of National Security")
then they started to BAN telegram....
 
Stopped working on netplus before 8 pm. BTW proton from fdroid lacks guest mode. Only play store version has that option. So much for privacy!
 
Reliance (AS18101) is doing BGP Hijack of Telegram!!!!

Following Pavel Durov's post alleging Reliance is hijacking Telegram's IP space via BGP, I decided to verify it independently using RIPE's routing data.

The result: confirmed.

RIPE's routing-status API for 91.108.56.0/22 (Telegram's IP block) shows two origin ASes:
  • AS62041 — Telegram, legitimate owner, has a proper RIPE route object ✅
  • AS18101 — Reliance, no route object, zero authorization ❌
A BGP origin without a route object means Reliance has no RIPE-registered right to announce this prefix. They're simply originating it anyway, and their upstream peers are accepting it.

Code:
curl "https://stat.ripe.net/data/routing-status/data.json?resource=91.108.56.0/22" | python3 -m json.tool

If you run the above command and check the origins array. AS18101 should not be there.

This is not a misconfiguration that persists for days unnoticed. BGP route objects exist precisely to prevent unauthorized announcements. Reliance has no excuse.

Network operators peering with AS18101 should filter this prefix immediately.
 
Back