Data as of Nov 11, 2026

87.229.178.0/24

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
21
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

638 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • NodeMaven
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.229.128.0/18
since Aug 2005
AS31359Mobile50
6 always on
PJSC "Vimpelcom"
87.229.128.0/17
since Feb 2009
AS31359Mobile302
38 always on
PJSC "Vimpelcom"

Registrations in this block

The registry's network records over this block, widest first, each 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.176.0/212,048RU-VimpelCom-HQ-IPv4PJSC "Vimpelcom" (ORG-ES15-RIPE) · RULIR-PARTITIONED PAFeb 26, 2014abuse-b2b@beeline.ru
└ 87.229.178.0/24256RU-GOLDENTELECOM-Client-Static-IP-Pool-NET111250 Russia SOVINTEL/EDN et GoldenTeleCOmASSIGNED PAMar 12, 2014abuse-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

87.229.176.0/21

Routing history

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