Data as of Nov 13, 2026

128.74.248.0/22

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Always-on exits
1
100% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
19
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

948 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • GloryCloud
  • InfiniteProxies
  • Kookey
  • Novada
  • Oxylabs
  • ProxyWing
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
128.72.0.0/14
since Dec 2011
AS8402Residential470
168 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
128.68.0.0 - 128.75.255.255524,288RU-CORBINA-20111031PJSC "Vimpelcom" (ORG-CTAM1-RIPE) · RUALLOCATED PANov 24, 2011abuse-b2b@beeline.ru
└ 128.74.0.0/1665,536BEELINE-BROADBANDDynamic IP Pool for Broadband CustomersASSIGNED PAOct 31, 2017abuse-b2b@beeline.ru
via RU-CORBINA-20111031

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
Sep 2014
Current origin since
Sep 2014 · 12 yr
Origin networks
1