Data as of Nov 13, 2026

87.225.0.0/21

478 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
478
23% of its addresses · 30 days
Spread
8 of 8
/24s with at least one exit
Providers
93
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

30K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NSocks
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.0.0/18
since Apr 2006
AS34584Residential2,821
5 always on
PJSC Rostelecom
87.225.0.0/17
since Feb 2007
AS34584Residential5,612
92 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
87.224.128.0 - 87.225.127.25565,536RU-RTK-20050614PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 18, 2013abuse@rt.ru
└ 87.225.0.0/23512KHT-XDSLp2p xDSL links in Khabarovsk city, ats-30 nodeASSIGNED PAJul 17, 2025abuse@rt.ru
via RU-RTK-20050614
└ 87.225.2.0/23512KHT-XDSLp2p xDSL links in Khabarovsk city, ats-21 nodeASSIGNED PAJul 17, 2025abuse@rt.ru
via RU-RTK-20050614
└ 87.225.4.0/23512KHT-XDSLp2p xDSL links in Khabarovsk city, ats-36 nodeASSIGNED PAJul 17, 2025abuse@rt.ru
via RU-RTK-20050614
└ 87.225.6.0/23512KHT-XDSLp2p xDSL links in Khabarovsk city, ats-51 nodeASSIGNED PAJul 17, 2025abuse@rt.ru
via RU-RTK-20050614

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
Feb 2007
Current origin since
Dec 2017 · 8.9 yr
Origin networks
2
Last change of origin
Dec 2017
Recorded history

History

Handoffs
1