Data as of Nov 11, 2026

128.75.232.0/24

25 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
25
9.8% of its addresses · 30 days
Providers
50
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
128.75.224.0/19
since Mar 2017
AS3216Residential469
166 always on
PJSC "Vimpelcom"
via 111250 Russia BeeLiNe
128.72.0.0/14
since Dec 2011
AS8402Residential470
167 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.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

Summary

Routing history

Pattern
Stable
First seen
Oct 2018
Current origin since
Oct 2018 · 8.1 yr
Origin networks
1