Data as of Nov 16, 2026

87.229.218.0/24

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
24
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

577 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.229.128.0/17
since Feb 2009
AS31359Mobile284
37 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.208.0/204,096RU-VimpelCom-HQ-IPv4PJSC "Vimpelcom" (ORG-ES15-RIPE) · RULIR-PARTITIONED PAOct 17, 2013abuse-b2b@beeline.ru
└ 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

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.208.0/20

Routing history

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