LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

80.201.45.0/24

9 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

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

Exits seen per day

7.2K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxio
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Thordata
  • VantageProxies
  • ZENPROXY_PREMIUM

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.201.32.0/204,096BE-SKYNET-ADSL1unknownASSIGNED PAMar 18, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

80.201.0.0/16

Routing history

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