Data as of Nov 15, 2026

217.136.176.0/24

3 residential-proxy exits · 30 days

Proximus NV

Announcement

217.136.0.0/16

RPKI valid

Announced by

AS5432

Type

Residential

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

1.2% of its addresses · 30 days

Always-on exits

33% of its exits

Providers

selling exits here

Oct 16, 2026 – Nov 14, 2026

Exits seen per day

4.6K observations

Proxy providers listing exits

711Proxy
AnyIP
BottingTools
ByteProxies
Byteful
DataImpulse
Decodo
Evomi
FlashProxy
FloppyData
GonzoProxy
IPRoyal
Infatica
InfiniteProxies
KindProxy
Oxylabs
Proxy-Seller
Proxy4U
ProxyRack
Proxyma
Thordata
Webshare

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
217.136.0.0/16	65,536	BE-BELGACOM-20010125	Proximus NV (ORG-BA4-RIPE) · BE	ALLOCATED PA	Dec 14, 2001	abuse@proximus.com
└ 217.136.176.0/22	1,024	BE-BELGACOM-ADSL1	unknown	ASSIGNED PA	Dec 4, 2007	abuse@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

Announcement Routing history RPKI & IRR Whois & 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

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
217.136.0.0/16	AS5432	/16	RIPE	RPKI valid

IRR

Route objects on 217.136.0.0/16

Origin	Registry	Description	Maintainer	Modified
AS5432	RIPE	SKYNETBE-CUSTOMERS	SKYNETBE-MNT	Sep 22, 2001