Data as of Nov 16, 2026

87.225.96.0/23

57 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI invalid (origin)
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
57
11% of its addresses · 30 days
Always-on exits
8
14% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
69
selling exits here
Oct 17, 2026 – Nov 14, 2026

Exits seen per day

19K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.225.97.0/24533
87.225.96.0/24324

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • 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,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.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

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.96.0/22

Routing history

First seen
Before our records
Origin networks
1