Data as of Nov 11, 2026

46.42.182.0/24

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
10
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

43 observations

Proxy providers listing exits

  • Byteful
  • EnigmaProxy
  • GSocks
  • IPFly
  • Infatica
  • NodeProxy
  • NovaProxy
  • Proxyma
  • PuraRoute
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.42.128.0/18
since Sep 2024
AS3216Residential2,544PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
46.42.128.0/1816,384RU-SOVINTEL-20100805PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAAug 5, 2010abuse-b2b@beeline.ru
└ 46.42.180.0/221,024RU-BeeLine-B2--IP-Pool-NET111250 Russia Moscow BeeLine et SOVINTEL/EDN et TatIntelLIR-PARTITIONED PASep 11, 2023abuse-b2b@beeline.ru
via RU-SOVINTEL-20100805

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

46.42.180.0/22

Routing history

Pattern
Stable
First seen
Apr 2026
Current origin since
Apr 2026 · 7 mo
Origin networks
1