Data as of Nov 10, 2026

178.23.4.0/22

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
14
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

24 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.23.4.0/2402
178.23.6.0/2401

Proxy providers listing exits

  • BottingTools
  • Byteful
  • GSocks
  • GonzoProxy
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • PuraRoute
  • Shifter
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each 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.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 178.23.0.0/21

178.23.0.0/21

Routing history

Pattern
Stable
First seen
Jan 2011
Current origin since
Jan 2011 · 16 yr
Origin networks
1