Data as of Nov 10, 2026

87.103.192.0/22

1 anonymizer address · 0.10% · VPN80 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
80
7.8% of its addresses · 30 days
Always-on exits
19
24% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
84
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

27K observations
  • VPN · anonymizer
  • Residential

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.103.193.0/24827
87.103.194.0/24621
87.103.192.0/24520
87.103.195.0/24012

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateByte
  • PrivateProxy
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
record created Oct 20, 2005 · reallocated to a party the registry does not name Dec 8, 2008
2 · Leased from
not leased
3 · Announced by
AS12389 PJSC Rostelecom
since Nov 2015 · 11.0 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 87.103.192.0/22/24s
VPN GateUniversity of Tsukuba
10.10%
1

Lineage

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

87.103.192.0/22

From the registry to its use

  1. Oct 20, 2005
    Registry record
    PJSC Rostelecom
    ALLOCATED PA
    87.103.128.0/17
  2. Dec 8, 2008
    Assigned
    OJSC "Sibirtelecom"
    ASSIGNED PA
    87.103.192.0/21
  3. Jul 8, 2010– Nov 8, 2015
    Announced
    AS41440 PJSC Rostelecom
  4. Nov 15, 2015– today
    Announced
    AS12389 PJSC Rostelecom
    Internet provider
  5. Oct 28, 2018– today
    Announced
    AS12389 PJSC Rostelecom
    as part of 87.103.128.0/17
    87.103.128.0/17
  6. Nov 1, 2018
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
  7. today
    Used
    VPN Gate
    VPN

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.103.128.0/17
since Oct 2018
AS12389Residential596
85 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.103.128.0/1732,768RU-RTK-20051020PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 20, 2005abuse@rt.ru
└ 87.103.192.0/198,192RU-SIBNETunknownLIR-PARTITIONED PADec 8, 2008abuse@rt.ru
via RU-RTK-20051020
└ 87.103.192.0/212,048WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PADec 8, 2008abuse@rt.ru
via RU-SIBNET

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

1,024 addresses
TypeAddressesShareRanges
Residential1,023>99%4
VPNanonymizer10.10%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jul 2010
Current origin since
Nov 2015 · 11 yr
Origin networks
2
Last change of origin
Nov 2015
Recorded history

History

Handoffs
1