Data as of Nov 10, 2026

89.112.3.0/24

4 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
35
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

370 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • KindProxy
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.112.0.0/15131,072RU-SOVINTEL-20060410PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAApr 10, 2006abuse-b2b@beeline.ru
└ 89.112.0.0/1732,768ZAO_ELTELnow PAO Vimpelcom - formely ZAO "ELTEL" (ORG-EA40-RIPE) · RULIR-PARTITIONED PAJul 5, 2012abuse-b2b@beeline.ru
└ 89.112.0.0/204,096ELTELPPPoE static address poolASSIGNED PAMay 14, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL

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

Who has announced 89.112.0.0/17

89.112.0.0/17

Routing history

Pattern
Stable
First seen
Feb 2010
Current origin since
Feb 2010 · 17 yr
Origin networks
1