Data as of Nov 16, 2026

62.231.24.0/24

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential
94% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
22
selling exits here
Oct 17, 2026 – Nov 14, 2026

Exits seen per day

550 observations

Proxy providers listing exits

  • BartProxies
  • BirdProxies
  • Byteful
  • EZProxies
  • EnigmaProxy
  • GSocks
  • Geonix
  • IPFly
  • IPPeak
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
62.231.0.0/198,192RU-SOVINTEL-20000719PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 17, 2001abuse-b2b@beeline.ru
└ 62.231.24.48/298RU-SOVINTEL-KND-Group-Demidov-NET401240 Russia KrasNoDar, ZC-4643905ASSIGNED PAMar 28, 2011abuse-b2b@beeline.ru
via RU-SOVINTEL-20000719
└ 62.231.24.104/298RU-SOVINTEL-NVR-CHEVRON-NEFTEGAZ-NET353900 Russia Novorossiysk, ZC-4612524ASSIGNED PADec 18, 2006abuse-b2b@beeline.ru
via RU-SOVINTEL-20000719

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential24094%3
Business166.3%2

Network & registry

Routing timeline

Who has announced 62.231.0.0/19

62.231.0.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1