Data as of Nov 20, 2026

89.188.242.0/24

5 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
5
2.0% of its addresses · 30 days
Providers
30
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

615 observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.188.224.0/19
since Jan 2009
AS20533Residential5PJSC "Vimpelcom"

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.188.224.0 - 89.189.31.25516,384RU-SOVINTEL-20060522PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJul 21, 2021abuse-b2b@beeline.ru
└ 89.188.236.0 - 89.188.243.2552,048SAKHTELSakhalin Telecom networkASSIGNED PADec 22, 2017abuse-b2b@beeline.ru
via RU-SOVINTEL-20060522

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

Summary

Routing history

Pattern
Stable
First seen
Apr 2008
Current origin since
Apr 2008 · 19 yr
Origin networks
1