Data as of Nov 10, 2026

91.147.16.0/24

42 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
42
16% of its addresses · 30 days
Always-on exits
1
2.4% of its exits
Providers
44
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

3.7K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PSBProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • 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.0.0/198,192SAKHALIN-YS-DYNAMIC1Rostelecom dynamic pool in Y.-SakhalinskASSIGNED PAJan 30, 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.0.0/19

Routing history

Pattern
Stable
First seen
Oct 2012
Current origin since
Dec 2018 · 7.9 yr
Origin networks
2
Last change of origin
Dec 2018
Recorded history

History

Handoffs
1