Data as of Nov 10, 2026

95.159.176.0/22

173 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
173
17% of its addresses · 30 days
Always-on exits
3
1.7% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
74
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

12K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.159.179.0/24241
95.159.177.0/24140
95.159.176.0/24049
95.159.178.0/24042

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • 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.176.0/221,024SAKHALIN-DYNAMIC-POOL8Rostelecom dynamic pool in SakhalinASSIGNED PANov 25, 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
Oct 2019 · 7.0 yr
Origin networks
2
Last change of origin
Dec 2018
Recorded history

History

Handoffs
1