Data as of Nov 16, 2026

95.73.72.0/21

10 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
10
0.49% of its addresses · 30 days
Spread
7 of 8
/24s with at least one exit
Providers
37
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

279 observations

/24s with the most always-on exits

Proxy providers listing exits

  • BartProxies
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • HPROXY
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • Proxies.fo
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.72.0.0/15
since Dec 2008
AS25515Residential17,678
25 always on
PJSC Rostelecom

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.71.0.0 - 95.73.255.255196,608RU-RTK-20081127PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 1, 2011abuse@rt.ru
└ 95.73.72.0/212,048CTC-Kolomna-NFKolomna netflow poolASSIGNED PAJun 16, 2009abuse@rt.ru
via RU-RTK-20081127

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

Summary

Routing history

Pattern
Stable
First seen
Dec 2010
Current origin since
Jul 2018 · 8.3 yr
Origin networks
2
Last change of origin
Jul 2018
Recorded history

History

Handoffs
1