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

87.225.96.0/22

71 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI invalid (origin)
Announced by
AS12389
Type
Residential

Residential-proxy exits

Proxy exits
71
6.9% of its addresses · 30 days
Always-on exits
8
11% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
64
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

25K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.225.97.0/24433
87.225.96.0/24224
87.225.98.0/24214

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.64.0/18
since Jul 2006
AS34584Residential2,791
87 always on
PJSC Rostelecom
87.225.0.0/17
since Feb 2007
AS34584Residential5,612
92 always on
PJSC Rostelecom
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
87.225.98.0/23
since Mar 2015
AS12389Residential14
2 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.96.0/2664KHT-XDSLstatic and PPPoE xDSL links in Sovetskaya Gavan town, central nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.96.64/2664KHT-XDSLstatic and PPPoE xDSL links in Sovetskaya Gavan town, central nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.96.128/25128KHT-XDSLstatic and PPPoE xDSL links in Sovetskaya Gavan town, central nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.97.0/25128KHT-XDSLstatic and PPPoE xDSL links in Viazemskivillage, central nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.97.192/2816KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-291 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.97.208/2816KHT-XDSLstatic and PPPoE xDSL links in Birobidjan town, ATS-711 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.98.0/25128KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-539 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.98.128/2664KHT-XDSLstatic and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-220 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.99.0/2664KHT-XDSLstatic and PPPoE xDSL links in Sovetskaya Gavan town, ATS-463 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

Summary

Routing history

First seen
Before our records
Origin networks
1