Data as of Nov 18, 2026

91.183.216.0/24

2 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
15
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

446 observations

Proxy providers listing exits

  • 9HTTP
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • Proxies.fo
  • Proxy-Seller
  • RainProxy
  • Shifter
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.180.0.0/14
since Sep 2006
AS5432Residential5,896
241 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.183.216.0/221,024BE-PRO-2012-08-30Pro 03CEN3ASSIGNED PAAug 30, 2012abuse@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.183.0.0/16

Routing history

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