Data as of Nov 21, 2026

217.136.114.0/24

8 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
46
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

1.5K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • HPROXY
  • HideProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • 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.112.0/212,048BE-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