Data as of Nov 11, 2026

95.159.168.0/22

184 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
184
18% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
70
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

12K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.159.171.0/24053
95.159.169.0/24050
95.159.168.0/24045
95.159.170.0/24036

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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
95.159.128.0/1816,384RU-RTK-20090424PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAApr 24, 2009abuse@rt.ru
└ 95.159.168.0/221,024SAKHALIN-DYNAMIC-POOL4Rostelecom dynamic pool in SakhalinASSIGNED PADec 21, 2009abuse@rt.ru
via RU-RTK-20090424

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

Who has announced this prefix

Summary

Routing history

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

History

Handoffs
1