Data as of Nov 17, 2026

87.229.242.0/24

27 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
27
11% of its addresses · 30 days
Providers
44
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

813 observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • GSocks
  • Geonix
  • GhostConnect
  • GonzoProxy
  • HPROXY
  • HideProxy
  • IPFly
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.229.224.0/19
since Jun 2013
AS3216Residential145
18 always on
PJSC "Vimpelcom"
via 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.224.0/198,192RU-Vimpelcom-HQ-IPv4PJSC "Vimpelcom" (ORG-ES15-RIPE) · RULIR-PARTITIONED PAJun 20, 2013abuse-b2b@beeline.ru
└ 87.229.242.0/24256RU-SOVINTEL-MSK-Wi-Fi-clients-IP-Pool-NET111250 Russia Mopscow SOVINTEL/EDNASSIGNED PASep 26, 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.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2015
Current origin since
Sep 2016 · 10 yr
Origin networks
1