Data as of Nov 20, 2026

128.75.224.0/24

5 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
25
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

793 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
128.72.0.0/14
since Dec 2011
AS8402Residential470
176 always on
PJSC "Vimpelcom"

Registrations in this block

The registry's network records over this block, widest first, each 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.75.224.0/198,192RU-BEELINE-B2O-Customers-IP-NET111250 Russia BeeLiNeSUB-ALLOCATED 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

128.75.224.0/19

Routing history

Pattern
Stable
First seen
Mar 2017
Current origin since
Mar 2017 · 9.6 yr
Origin networks
1