Data as of Nov 17, 2026

80.201.167.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
32
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

850 observations

Proxy providers listing exits

  • AnyIP
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • ProxiesVision
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.200.0.0/15
since May 2005
AS5432Residential3,394
169 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.164.0/221,024BE-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

RPKI

Route origin authorizations

ROA prefixASNMax lenAnchorVerdict
80.200.0.0/15AS5432/16RIPERPKI valid
IRR

Route objects on 80.201.0.0/16

OriginRegistryDescriptionMaintainerModified
AS5432 RIPEFIA-003SKYNETBE-MNTSep 28, 2022