Data as of Nov 15, 2026

87.229.208.0/20

44 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
88% of it

Residential-proxy exits

Proxy exits
44
1.1% of its addresses · 30 days
Always-on exits
9
20% of its exits
Spread
14 of 16
/24s with at least one exit
Providers
81
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

18K observations
  • Residential
  • Business

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LUMIPROXY
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXY_CC
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.229.128.0/17
since Feb 2009
AS31359Mobile289
37 always on
PJSC "Vimpelcom"

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.229.128.0/1732,768RU-SOVINTEL-20050722PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJul 22, 2005abuse-b2b@beeline.ru
└ 87.229.208.0/204,096RU-VimpelCom-HQ-IPv4PJSC "Vimpelcom" (ORG-ES15-RIPE) · RULIR-PARTITIONED PAOct 17, 2013abuse-b2b@beeline.ru
└ 87.229.208.0/24256RU-SOVINTEL-EDN-B2B-client-pool-NET111250 Russia SOVINTEL/EDN et ForatecASSIGNED PAOct 31, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.209.0/24256RU-GoldenTeleCom-LoopBacks-IP-Pool-NET111250 Russia Moscow SOVINTEL/EDNASSIGNED PAOct 31, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.210.0/24256RU-SOVINTEL-P2P-Client-IP-NET111250 Russia SOVINTEL/EDNASSIGNED PANov 1, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.211.0/24256RU-GoldenTeleCom-Client-IP-Pool-NET111250 Russia Moscow SOVINTEL/EDNASSIGNED PANov 1, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.212.0/24256RU-SOVINTEL-EDN-B2B-client-pool-NET111250 Russia SOVINTEL/EDN et ForatecASSIGNED PAMay 3, 2023abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.213.0/24256RU-SovamTelePort-P2P-Static-IP-Pool-NET111250 Russia SOVINTEL/EDN et SovamTelePortASSIGNED PANov 26, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.214.0/24256RU-GOLDENTELECOM-Client-Static-IP-Pool-NET111250 Russia SOVINTEL/EDN et GoldenTeleCOmASSIGNED PANov 26, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.216.0/24256RU-SOVINTEL-P2P-Client-IP-pool-NET111250 Russia SOVINTEL/EDNASSIGNED PADec 3, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.217.0/24256RU-SovamTelePort-P2P-Static-IP-Pool-NET111250 Russia SOVINTEL/EDN et SovamTelePortASSIGNED PADec 3, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.218.0/24256RU-GOLDENTELECOM-Client-Static-IP-Pool-NET111250 Russia SOVINTEL/EDN et GoldenTeleCOmASSIGNED PADec 3, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.219.0/24256RU-SOVINTEL-Foratec-p2p-IP-Pool-NET111250 Russia SOVINTEL/EDN et ForatecASSIGNED PADec 3, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.220.0/24256RU-SOVINTEL-Wi-Fi-clients-IPv4-pool-NET111250 Russia EDN/SOVINTELASSIGNED PAApr 9, 2014abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.221.0/24256RU-SovamTelePort-P2P-Clients-IP-Pool-NET111250 Russia SOVINTEL/EDN et SovamTelePortASSIGNED PADec 12, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.222.0/24256RU-GOLDENTELECOM-Client-Static-IP-Pool-NET111250 Russia SOVINTEL/EDN et GoldenTeleCOmASSIGNED PADec 12, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4
└ 87.229.223.0/24256RU-SOVINTEL-Foratec-p2p-static-IP-Pool-NET111250 Russia SOVINTEL/EDN et ForatecASSIGNED PADec 12, 2013abuse-b2b@beeline.ru
via RU-VimpelCom-HQ-IPv4

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

4,096 addresses
TypeAddressesShareRanges
Residential3,58488%2
Business51213%2

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2013
Current origin since
Nov 2013 · 13 yr
Origin networks
1