Data as of Nov 21, 2026

62.231.1.104/29

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
1
13% of its addresses · 30 days
Providers
23
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

20 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • IPFly
  • IPROCKET_PREMIUM
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • SOTAPROXY
  • Shifter
  • 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.1.104/298RU-SOVINTEL-MSK-GlavKom-NET121170 Russia Moscow, ZC-6740226ASSIGNED PASep 12, 2013abuse-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

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