Data as of Nov 18, 2026

91.181.111.0/24

7 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
49
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

6.0K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • HASDATA
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSTPROXY_LITE
  • NSTPROXY_PRIME
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • Q2IP
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.180.0.0/14
since Sep 2006
AS5432Residential5,900
238 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.96.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

Routing timeline

Covering aggregate above, the prefix's own history below

91.181.0.0/16

Routing history

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