Data as of Nov 21, 2026

109.140.103.0/24

41 residential-proxy exits · 30 days

Proximus NV

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
41
16% of its addresses · 30 days
Providers
36
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

258 observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • B2Proxy
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • Geonode
  • GloryCloud
  • HPROXY
  • HideProxy
  • IPPeak
  • InfiniteProxies
  • KocerRoxy
  • LudaxProxy
  • MoMoProxy
  • NextProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
109.140.0.0/14
since Aug 2009
AS5432Residential10,717Proximus 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.139.0.0 - 109.140.255.255131,072BE-BELGACOM-MOBILE-INTERNETProximus Mobile InternetASSIGNED PADec 20, 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.140.0.0/16

Routing history

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