Data as of Nov 21, 2026

109.133.74.0/24

5 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
24
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

4.4K observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_BASIC
  • BUYPERSONALPROXY
  • BottingTools
  • CatProxies
  • CliProxy
  • FLAMEPROXIES_BASIC
  • GEEKPROXY_TURBO
  • Geonode
  • HASDATA
  • HPROXY
  • HideProxy
  • InfiniteProxies
  • LudaxProxy
  • NSTPROXY_PRIME
  • PROXYSAVER
  • PROXYSCRAPE
  • Proxies.fo
  • ProxyGeo
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
109.132.0.0/14
since Aug 2009
AS5432Residential5,602
233 always on
Proximus NV

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
109.128.0.0/121,048,576BE-BELGACOM-20090727Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PAJul 27, 2009abuse@proximus.com
└ 109.133.0.0/1665,536BE-BELGACOM-ADSL1unknownASSIGNED PANov 25, 2011abuse@proximus.com
via BE-BELGACOM-20090727

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

109.133.0.0/16

Routing history

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