Data as of Nov 10, 2026

77.41.182.0/24

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address
Recent change
New origin Oct 1, 2026
its first announcement on record

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
5
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

7 observations

Proxy providers listing exits

  • GSocks
  • LemonPrime
  • MangoProxy
  • Proxy-Seller
  • Proxyma

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.41.160.0/19
since Apr 2014
AS3216Residential72
14 always on
PJSC "Vimpelcom"
via 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.41.128.0/1732,768RU-SOVINTEL-20061201PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 1, 2006abuse-b2b@beeline.ru
└ 77.41.160.0/198,192RU-VimpelCom-former-IzSvyazInvest-IPv4-POOLPJSC "Vimpelcom" (ORG-ES15-RIPE) · RULIR-PARTITIONED PAApr 11, 2014abuse-b2b@beeline.ru
└ 77.41.182.0/24256RU-EDN-Sovintel-BeeCLOUD-Pool-NET111250 Russia SOVINTEL/EDNASSIGNED PADec 10, 2018abuse-b2b@beeline.ru
via RU-VimpelCom-former-IzSvyazInvest-IPv4-POOL

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

Summary

Routing history

Pattern
Stable
First seen
Oct 1, 2026
Current origin since
Oct 1, 2026 · 1 mo
Origin networks
1