Data as of Nov 16, 2026

217.136.50.0/24

4 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
43
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

18K observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • LOKIPROXY
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VitalExclusive

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.48.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PAMar 21, 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

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