Data as of Nov 12, 2026

91.183.124.0/22

8 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
8
0.78% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
30
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

172 observations

/24s with the most always-on exits

Proxy providers listing exits

  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BottingTools
  • CatProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • Kookey
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy302
  • RainProxy
  • RoamProxy
  • SPYDERPROXY_BASIC
  • SwiftProxy
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.180.0.0/14
since Sep 2006
AS5432Residential5,681
284 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.124.0/221,024BE-PRO-2012-01-17Office msr03bkc3ASSIGNED PAJan 17, 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