Data as of Nov 21, 2026

77.106.197.0/24

5 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
29
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

3.7K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.106.192.0/18
since Jan 2007
AS42110Residential15
2 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.106.192.0/1816,384RU-SOVINTEL-20061215PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 15, 2006abuse-b2b@beeline.ru
└ 77.106.196.0/23512RU-EDN-SOVINTEL-p2p-Customer-Pool-NET111250 Russia Moscow SOVINTEL/EDN et SochyTelASSIGNED PADec 25, 2017abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215

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

Covering aggregate above, the prefix's own history below

77.106.196.0/23

Routing history

Pattern
Stable
First seen
Dec 2017
Current origin since
Dec 2017 · 8.9 yr
Origin networks
1