Data as of Nov 14, 2026

210.212.69.0/24

3 residential-proxy exits · 30 days

National Internet Backbone · space held by Bharat Sanchar Nigam Ltd

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
35
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

220 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • APROXY
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FastProxy
  • FlexyProxies
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NiuProxy
  • PROXY_CC
  • PrivateProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VitalData
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
210.212.64.0/20
since May 2005
AS9829Residential17Bharat Sanchar Nigam Ltd

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
210.212.0.0/1665,536BSNLNETBharat Sanchar Nigam Ltd (ORG-BSNL1-AP) · INALLOCATED PORTABLE—abuse1@bsnl.co.in
└ 210.212.69.32/304Railtel-BSNL-PEERINGRailtelASSIGNED NON-PORTABLE—abuse1@bsnl.co.in
└ 210.212.69.48/304IOBindian overseas bankASSIGNED NON-PORTABLE—abuse1@bsnl.co.in
└ 210.212.69.148/304TANGEDCOTangedco Head QTRS Data CentreASSIGNED NON-PORTABLE—abuse1@bsnl.co.in
└ 210.212.69.172/304unipartsUNIPARTSGROUPASSIGNED NON-PORTABLE—abuse1@bsnl.co.in
via BSNLNET
└ 210.212.69.184 - 210.212.69.25572RDMATVLNETRegional Director of Municipal AdministrationASSIGNED NON-PORTABLE—abuse1@bsnl.co.in
via BSNLNET

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2015
Current origin since
Jan 2015 · 12 yr
Origin networks
1