Data as of Nov 11, 2026

89.113.4.0/22

4 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
23
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

142 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.113.4.0/2402
89.113.6.0/2401
89.113.7.0/2401

Proxy providers listing exits

  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

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.113.0.0/212,048IP-static-mob-1Pool #1 for static IP-address services for mobile customers by Order#3222PLIR-PARTITIONED PAOct 23, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-20060410
└ 89.113.4.0/221,024BEE_STATICPool for static IP-address services for mobile customersASSIGNED PADec 13, 2013abuse-b2b@beeline.ru
via IP-static-mob-1

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 2014
Current origin since
Feb 2014 · 13 yr
Origin networks
1