Data as of Nov 10, 2026

80.200.232.0/24

10 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Providers
30
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

737 observations

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • BuyingProxy
  • CliProxy
  • Datarama
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.200.0.0/15
since May 2005
AS5432Residential3,226
257 always on
Proximus NV

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.200.0.0/15131,072BE-BELGACOM-20011108Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PANov 8, 2001abuse@proximus.com
└ 80.200.224.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PAMar 21, 2005abuse@proximus.com
via BE-BELGACOM-20011108

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

80.200.0.0/16

Routing history

Pattern
Stable
First seen
Oct 2022
Current origin since
Oct 2022 · 4.0 yr
Origin networks
1