Data as of Nov 22, 2026

62.231.27.248/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
Always-on exits
1
100% of its exits
Providers
24
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

12 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter

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.27.248/298RU-SOVINTEL-MSK-Soyuz-Divinil-NET117036 Russia Moscow, ZC-4515154ASSIGNED PAJan 21, 2011abuse-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