LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

212.20.2.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
212.20.0.0/18
RPKI valid
Announced by
AS12389
Type
Business

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
18
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

81 observations

Proxy providers listing exits

  • BartProxies
  • ByteProxies
  • Byteful
  • Evomi
  • GSocks
  • Geonix
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.20.0.0/1816,384RU-RTK-980220PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 28, 2002abuse@rt.ru
└ 212.20.2.0/24256RU-RTK-980220unknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-980220
└ 212.20.2.0/25128RINET-TURBORINET-TURBO officeASSIGNED PAOct 14, 2010abuse@rt.ru
via RU-RTK-980220
└ 212.20.2.128/2664RINET-TURBOOJSC RINet, Novosibirsk, RussiaASSIGNED PA—abuse@rt.ru
via RU-RTK-980220
└ 212.20.2.192/2664RINET-TURBOOJSC RINet, Novosibirsk, RussiaASSIGNED PA—abuse@rt.ru
via RU-RTK-980220

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 212.20.0.0/18

212.20.0.0/18

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Aug 2016 · 10 yr
Origin networks
3
Last change of origin
Aug 2016
Recorded history

History

Handoffs
2