LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

62.231.18.72/29

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

Announcement
62.231.0.0/19
No RPKI
Announced by
AS3216
Type
Business
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
1
13% of its addresses · 30 days
Always-on exits
4
100% of its exits
Providers
52
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

569 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • IPPeak
  • Infatica
  • Kookey
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

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.18.72/298RU-SOVINTEL-MSK-RoSKoMMuNeNeRGo-NET125184 Russia Moscow, ZC- 10351328ASSIGNED PAOct 26, 2017abuse-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.

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
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