Data as of Nov 16, 2026

87.225.124.0/23

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

Exits seen per day

8.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.225.124.0/24066
87.225.125.0/24062

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LOKIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.64.0/18
since Jul 2006
AS34584Residential2,799
90 always on
PJSC Rostelecom
87.225.0.0/17
since Feb 2007
AS34584Residential5,647
94 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.124.0/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-34 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.124.64/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-21 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.124.128/25128KHT-XDSLstatic and PPPoE xDSL links in Bogorodskoe village, central nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.125.0/25128KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-21 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.125.128/25128KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-533 nodeASSIGNED PADec 29, 2007abuse@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
Sep 2015
Current origin since
Sep 2015 · 11 yr
Origin networks
1