Data as of Nov 16, 2026

87.225.18.0/23

115 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
115
22% of its addresses · 30 days
Always-on exits
1
0.87% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
72
selling exits here
Oct 17, 2026 – Nov 14, 2026

Exits seen per day

11K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.225.18.0/24152
87.225.19.0/24068

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.0.0/18
since Apr 2006
AS34584Residential2,848
4 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.18.0/2732KHT-XDSLstatic and PPPoE xDSL links in Nikolaevsk-at-Amur town , ATS-51 nodeASSIGNED PADec 13, 2005abuse@rt.ru
via RU-RTK-20050614
└ 87.225.18.32/2732KHT-XDSLstatic and PPPoE xDSL links in Polina Osipenko village , central nodeASSIGNED PADec 13, 2005abuse@rt.ru
via RU-RTK-20050614
└ 87.225.18.64/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, HONET-26 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.18.96/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, HONET-61 nodeASSIGNED PADec 25, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.18.128/2664KHT-XDSLstatic and PPPoE xDSL links in Bogorodskoe village, cental nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.19.0/24256KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-30 nodeASSIGNED PADec 28, 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
Jun 2007
Current origin since
Dec 2017 · 8.9 yr
Origin networks
2
Last change of origin
Dec 2017
Recorded history

History

Handoffs
1