LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

87.225.86.0/24

59 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
59
23% of its addresses · 30 days
Always-on exits
1
1.7% of its exits
Providers
70
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

9.9K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HELODATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Smartproxy
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TrueProxies
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.80.0/20
since Mar 2010
AS34584Residential819
15 always on
PJSC Rostelecom
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 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.86.0/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-293 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.86.128/2732KHT-XDSLstatic and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-274 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.86.160/2732KHT-XDSLstatic and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-275 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.86.192/2732KHT-XDSLstatic and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-2761 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.86.224/2732KHT-XDSLstatic and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-2762 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

87.225.80.0/21

Routing history

Pattern
Stable
First seen
Mar 2007
Current origin since
Dec 2017 · 8.9 yr
Origin networks
2
Last change of origin
Dec 2017
Recorded history

History

Handoffs
1