Data as of Nov 20, 2026

87.225.62.0/24

53 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
53
21% of its addresses · 30 days
Providers
71
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

5.0K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HideProxy
  • IPFly
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.0.0/18
since Apr 2006
AS34584Residential2,833
9 always on
PJSC Rostelecom
87.225.0.0/17
since Feb 2007
AS34584Residential5,591
99 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each 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.62.0/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, DLC-1 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.62.32/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, DLC-1 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.62.64/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, DLC-3 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.62.96/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, DLC-3 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.62.128/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, DLC-4 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.62.160/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, DLC-4 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.62.192/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, DLC-5 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.62.224/2732KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, DLC-5 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

87.225.60.0/22

Routing history

Pattern
Stable
First seen
Jun 2016
Current origin since
Jun 2016 · 10 yr
Origin networks
1