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

217.136.2.0/24

10 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Always-on exits
4
40% of its exits
Providers
41
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

11K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GhostConnect
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • LudaxProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • SPYDERPROXY_PREMIUM
  • StrikeProxy
  • Thordata
  • VantageProxies
  • Webshare
  • ZENPROXY_PREMIUM

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.0.0/198,192BE-SKYNET-ADSL1unknownASSIGNED PAMar 18, 2005abuse@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