Data as of Nov 18, 2026

77.106.192.0/18

15 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
94% of it

Residential-proxy exits

Proxy exits
15
0.09% of its addresses · 30 days
Always-on exits
2
13% of its exits
Spread
4 of 64
/24s with at least one exit
Providers
56
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

10K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
77.106.196.0/23
since Dec 2017
AS3216Residential6
1 always on
PJSC "Vimpelcom"
77.106.248.0/22
since May 2019
AS42110Residential1PJSC "Vimpelcom"
77.106.252.0/22
since Apr 2019
AS42110Residential8
1 always on
PJSC "Vimpelcom"

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, 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.192.0/221,024RU-SOVINTEL-SOCHITEL-B2B-NETex-ZAO SochitelecomASSIGNED PADec 25, 2017abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 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
└ 77.106.198.0 - 77.106.223.2556,656RU-BEELINE-SOCHITEL-101-NETex-ZAO SochitelecomASSIGNED PADec 25, 2017abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.224.0/212,048SOCHITEL-101ex ZAO SochitelecomASSIGNED PADec 18, 2006abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.232.0/23512SOCHITEL-101ZAO SochitelecomASSIGNED PADec 18, 2006abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.234.0/23512SOCHITEL_FTTBFTTB customersASSIGNED PANov 12, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.236.0/24256SOCHITEL-101Sochitel mgmt networkASSIGNED PANov 12, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.237.0/24256SOCHITEL-101For customers at Golubye DaliASSIGNED PANov 12, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.238.0/23512SOCHITEL_FTTBFTTB customersASSIGNED PANov 12, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.240.0/221,024SOCHITEL_FTTBFTTB customersASSIGNED PANov 13, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.244.0/221,024Sochi_broadbandSochi IP address pool for BRASesASSIGNED PANov 20, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.248.0/221,024Sochi_broadbandSochi IP address pool for BRASesASSIGNED PANov 20, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-20061215
└ 77.106.252.0/221,024RU-beeline-Sochi_broadband-NETSochi IP address pool for BRASesASSIGNED PANov 20, 2013abuse-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.

Composition

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

Announced space

Address share

Announced space

Types across the prefix

16,384 addresses
TypeAddressesShareRanges
Residential15,36094%4
Business1,0246.3%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2007
Current origin since
Jan 2007 · 20 yr
Origin networks
1