Data as of Nov 19, 2026

91.180.236.0/24

3 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
16
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • BottingTools
  • Byteful
  • CliProxy
  • Decodo
  • LemonBright
  • LudaxProxy
  • Oxylabs
  • ProxiesVision
  • ProxyGeo
  • RainProxy
  • SPYDERPROXY_BASIC
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.180.0.0/14
since Sep 2006
AS5432Residential5,885
239 always on
Proximus NV

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
91.176.0.0/13524,288BE-BELGACOM-20060904Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PASep 4, 2006abuse@proximus.com
└ 91.180.224.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PAMay 7, 2009abuse@proximus.com
via BE-BELGACOM-20060904

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

91.180.0.0/16

Routing history

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