Data as of Nov 16, 2026

212.91.196.0/24

24 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
24
9.4% of its addresses · 30 days
Providers
33
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

407 observations

Proxy providers listing exits

  • Ake.net
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • Geonode
  • GhostConnect
  • HideProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • KindProxy
  • NovProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • VantageProxies
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.91.192.0/20
since May 2005
AS12332Residential100PJSC Rostelecom
212.91.192.0/19
since May 2005
AS12332Residential207PJSC 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.91.192.0/198,192RU-RTK-990518PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 14, 2001abuse@rt.ru
└ 212.91.196.0/24256VRANGELNETNeocom Co.,Ltd.ASSIGNED PANov 14, 2001abuse@rt.ru
via RU-RTK-990518

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
Oct 2014
Current origin since
Sep 2020 · 6.1 yr
Origin networks
1