Data as of Nov 10, 2026

217.136.231.0/24

3 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
11
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

875 observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • BottingTools
  • Decodo
  • FloppyData
  • IPFly
  • Novada
  • Oxylabs
  • PuraRoute
  • Thordata
  • Webshare

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.230.0/23512BE-SKYNET-20011108unknownASSIGNED 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

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