Data as of Nov 18, 2026

217.136.81.0/24

6 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
36
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

820 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • IPFly
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NSTPROXY_LITE
  • NSTPROXY_PRIME
  • NodeProxy
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxyma
  • PuraRoute
  • Q2IP
  • SOTAPROXY
  • Shifter
  • Thordata
  • 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.80.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