Data as of Nov 11, 2026

80.95.44.0/23

512 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
512
100% of its addresses · 30 days
Always-on exits
208
41% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
47
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

392K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.95.44.0/24105254
80.95.45.0/24103253

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MarsProxies
  • Maskify
  • NSocks
  • Novada
  • Oxylabs
  • PacketStream
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.95.32.0/204,096RU-RTK-20011004PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 22, 2002abuse@rt.ru
└ 80.95.44.0/23512MRF-VOLGA-PENZA-DYNPOOL-25-03-2013-2Dyn. address space for broadband usersASSIGNED PANov 23, 2012abuse@rt.ru
via RU-RTK-20011004

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 80.95.32.0/20

80.95.32.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2016 · 11 yr
Origin networks
2
Last change of origin
May 2016
Recorded history

History

Handoffs
1