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

87.225.64.0/21

1 anonymizer address · 0.05% · VPN480 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS12389
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
480
23% of its addresses · 30 days
Spread
8 of 8
/24s with at least one exit
Providers
100
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

34K observations
  • VPN · anonymizer
  • Residential

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.225.67.0/24064
87.225.64.0/24063
87.225.66.0/24063
87.225.65.0/24059
87.225.68.0/24059
87.225.70.0/24059
87.225.71.0/24058
87.225.69.0/24056

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NSocks
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYFALL
  • PROXYLANE
  • PROXYON
  • PROXYSALE
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PYPROXY
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SIMPLYNODE
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
PJSC Rostelecom
record created Nov 18, 2013
2 · Leased from
not leased
3 · Announced by
AS12389 PJSC Rostelecom
since Jun 2016 · 10.4 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 87.225.64.0/21/24s
VPN GateUniversity of Tsukuba
10.05%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

87.225.64.0/21

From the registry to its use

  1. Jul 1, 2006– today
    Announced
    AS34584 PJSC Rostelecom
    as part of 87.225.64.0/18
    87.225.64.0/18
  2. Nov 18, 2013
    Registry record
    PJSC Rostelecom
    ALLOCATED PA
    87.224.128.0 - 87.225.127.255
  3. Jun 15, 2016– today
    Announced
    AS12389 PJSC Rostelecom
    Internet provider
  4. Oct 18, 2018
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
  5. today
    Used
    VPN Gate
    VPN

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.64.0/18
since Jul 2006
AS34584Residential2,778
88 always on
PJSC Rostelecom
87.225.0.0/17
since Feb 2007
AS34584Residential5,575
92 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.64.0/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-494 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.64.64/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-494 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.64.128/2664KHT-XDSLstatic and PPPoE xDSL links in Mayak village, central nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.64.192/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-291 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.65.0/24256KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-30 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.66.0/24256KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-30 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.67.0/24256KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-30 nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.68.0/24256KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, central nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.69.0/24256KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, central nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.70.0/24256KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, central nodeASSIGNED PADec 28, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.71.0/24256KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, central 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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Residential2,047>99%2
VPNanonymizer10.05%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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