Data as of Nov 11, 2026

178.23.0.0/21

25 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
25
1.2% of its addresses · 30 days
Always-on exits
1
4.0% of its exits
Spread
4 of 8
/24s with at least one exit
Providers
37
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.23.1.0/24111
178.23.0.0/24011
178.23.4.0/2402
178.23.6.0/2401

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonLabs
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

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
178.23.0.0/212,048RU-SOVINTEL-20100416PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAApr 16, 2010abuse-b2b@beeline.ru
└ 178.23.0.0/221,024VYMPELCOM-FTTB-MURMANSK-1Vympelcom (former PolarCom Ltd)ASSIGNED PADec 16, 2011abuse-b2b@beeline.ru
via RU-SOVINTEL-20100416
└ 178.23.4.0/221,024VYMPELCOM-FTTB-MURMANSK-2Vympelcom (former PolarCom Ltd)ASSIGNED PADec 16, 2011abuse-b2b@beeline.ru
via RU-SOVINTEL-20100416

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
Jan 2011
Current origin since
Jan 2011 · 16 yr
Origin networks
1