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

212.96.201.0/24

21 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
212.96.192.0/19
RPKI valid
Announced by
AS12389
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
21
8.2% of its addresses · 30 days
Always-on exits
4
19% of its exits
Providers
50
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

5.1K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.96.192.0/198,192RU-RTK-990420PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAApr 23, 2002abuse@rt.ru
└ 212.96.201.0/24256WSNETKhanty-Mansyisk territorial nodeASSIGNED PAMar 17, 2006abuse@rt.ru
via RU-RTK-990420

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.96.192.0/19

212.96.192.0/19

Routing history

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

History

Handoffs
2