Data as of Nov 16, 2026

77.106.252.0/24

8 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
39
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

6.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • VitalProxy

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.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.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

77.106.252.0/22

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Apr 2019 · 7.6 yr
Origin networks
1