LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

109.135.4.0/22

4 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
24
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
109.135.6.0/2402
109.135.4.0/2401
109.135.5.0/2401

Proxy providers listing exits

  • 9Proxy
  • AnyIP
  • BlurPath
  • BottingTools
  • CatProxies
  • CliProxy
  • FastProxy
  • FloppyData
  • Geonode
  • IPFly
  • InfiniteProxies
  • Kookey
  • LemonBright
  • NovProxy
  • NovaProxy
  • Novada
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SwiftProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
109.132.0.0/14
since Aug 2009
AS5432Residential5,663
232 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.4.0/221,024BE-PRO-2013-03-22Pro 91GKK3ASSIGNED PAMar 22, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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.0 yr
Origin networks
1