Data as of Nov 12, 2026

212.32.217.0/24

256 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby
Recent change
New origin Jul 2026
its first announcement on record

Residential-proxy exits

Proxy exits
256
100% of its addresses · 30 days
Always-on exits
149
58% of its exits
Providers
41
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

304K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • Maskify
  • NSocks
  • NodeMaven
  • Novada
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.32.192.0/19
since Jun 2016
AS12389Residential1,564
990 always on
PJSC Rostelecom

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
212.32.192.0/198,192RU-RTK-980805PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PA—abuse@rt.ru
└ 212.32.217.0/24256samtelNetwork of the SF OAO "VolgaTelecom"ASSIGNED PAMar 31, 2005abuse@rt.ru
via RU-RTK-980805

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
Jul 2026
Current origin since
Jul 2026 · 4 mo
Origin networks
1