Data as of Nov 22, 2026

109.134.74.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
37
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • Decodo
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GoProxies
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
109.132.0.0/14
since Aug 2009
AS5432Residential5,574
234 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.134.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.134.0.0/16

Routing history

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