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

217.136.153.0/24

12 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
54
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

379 observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SpyderProxy
  • TalorData
  • ThunderProxy
  • TrustProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.136.0.0/1665,536BE-BELGACOM-20010125Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PADec 14, 2001abuse@proximus.com
└ 217.136.144.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PADec 4, 2007abuse@proximus.com
via BE-BELGACOM-20010125

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

Who has announced 217.136.0.0/16

217.136.0.0/16

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1