Data as of Nov 17, 2026

87.229.142.0/23

8 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
8
1.6% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
38
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

330 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.229.143.0/2406
87.229.142.0/2402

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.229.128.0/18
since Aug 2005
AS31359Mobile45
4 always on
PJSC "Vimpelcom"
87.229.128.0/17
since Feb 2009
AS31359Mobile284
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.142.0 - 87.229.143.0257RU-SOVINTEL-HQ-IPv4PJSC "Vimpelcom" (ORG-ES15-RIPE) · RULIR-PARTITIONED PAApr 10, 2014abuse-b2b@beeline.ru
└ 87.229.142.0/24256RU-SOVINTEL-Wi-Max-Static-IPv4-pool-NET111250 Russia EDN/SOVINTELASSIGNED PAApr 10, 2014abuse-b2b@beeline.ru
via RU-SOVINTEL-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.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Apr 2014
Current origin since
Apr 2014 · 13 yr
Origin networks
1