Data as of Nov 10, 2026

91.147.35.0/24

32 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
32
13% of its addresses · 30 days
Providers
39
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.9K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • GSocks
  • Geonix
  • Geonode
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.147.0.0/18
since Nov 2023
AS12389Residential2,115
16 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
91.147.0.0/1816,384RU-RTK-20061024PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 24, 2006abuse@rt.ru
└ 91.147.34.0/23512SAKHALIN-POOL-N2Sakhalin dynamic poolASSIGNED PAAug 6, 2007abuse@rt.ru
via RU-RTK-20061024

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

91.147.34.0/23

Routing history

Pattern
Stable
First seen
Jan 2008
Current origin since
Sep 2021 · 5.2 yr
Origin networks
2
Last change of origin
Sep 2021
Recorded history

History

Handoffs
1