Data as of Nov 20, 2026

81.240.154.0/24

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
3.1% of its addresses · 30 days
Always-on exits
2
25% of its exits
Providers
44
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

21K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Decodo
  • EZProxies
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • GEEKPROXY_TURBO
  • HELODATA
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • KocerRoxy
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxio
  • Proxiware
  • Proxy302
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.240.0.0/14
since May 2005
AS5432Residential6,508
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
81.240.0.0/13524,288BE-BELGACOM-20021129Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PAOct 27, 2003abuse@proximus.com
└ 81.240.144.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PAMar 21, 2005abuse@proximus.com
via BE-BELGACOM-20021129

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

81.240.0.0/16

Routing history

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