Data as of Nov 21, 2026

91.181.167.0/24

6 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
38
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

82 observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • Ake.net
  • AnyIP
  • B2Proxy
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • Proxies.fo
  • Proxy-Seller
  • Proxy4U
  • Proxyma
  • PuraRoute
  • Q2IP
  • Shifter
  • Thordata
  • Webshare
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.180.0.0/14
since Sep 2006
AS5432Residential5,838
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.181.160.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PAFeb 24, 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

RPKI

Route origin authorizations

ROA prefixASNMax lenAnchorVerdict
91.180.0.0/14AS5432/16RIPERPKI valid
IRR

Route objects on 91.181.0.0/16

OriginRegistryDescriptionMaintainerModified
AS5432 RIPEFIA-013SKYNETBE-MNTSep 28, 2022