Data as of Nov 20, 2026

109.135.0.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
30
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • AnyIP
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • Infatica
  • LemonBright
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
109.132.0.0/14
since Aug 2009
AS5432Residential5,628
235 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.135.0.0/221,024BE-PRO-2013-03-01Pro 02MAR3ASSIGNED PAMar 1, 2013abuse@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.135.0.0/16

Routing history

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