Data as of Nov 10, 2026

91.182.167.0/24

5 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
17
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

226 observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BottingTools
  • EZProxies
  • FastProxy
  • IPFly
  • IPPeak
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • Novada
  • RainProxy
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.180.0.0/14
since Sep 2006
AS5432Residential5,594
379 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.182.160.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PAMar 31, 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.182.0.0/16

Routing history

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