Data as of Nov 11, 2026

89.112.0.0/17

34 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
34
0.10% of its addresses · 30 days
Always-on exits
3
8.8% of its exits
Spread
14 of 128
/24s with at least one exit
Providers
57
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

7.4K observations

Proxy providers listing exits

  • 2Captcha
  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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
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
└ 89.112.16.0/212,048ELTEL_PPPoE_static-NETELTEL PPPoE static IP-pool for b2b customersASSIGNED PANov 10, 2014abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.24.0/212,048ELTELPPPoE dynamic address poolASSIGNED PAMay 14, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.32.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.36.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.40.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.44.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.48.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.52.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.56.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.60.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.64.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.68.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.72.0/221,024ELTELPPPoE dynamic address poolASSIGNED PAJun 25, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.76.0/221,024ELTELPPPoE address poolASSIGNED PAMay 31, 2013abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.80.0/212,048ELTELPPPoE dynamic address poolASSIGNED PAMay 14, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.88.0/212,048ELTELPPPoE dynamic address poolASSIGNED PAMay 14, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.96.0/212,048ELTELPPPoE dynamic address poolASSIGNED PAMay 14, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.104.0/212,048ELTELPPPoE dynamic address poolASSIGNED PAMay 14, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.112.0/212,048ELTELPPPoE dynamic address poolASSIGNED PAMay 14, 2012abuse-b2b@beeline.ru
via ZAO_ELTEL
└ 89.112.120.0/212,048ELTELPPPoE dynamic 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 this prefix

Summary

Routing history

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