Data as of Nov 11, 2026

87.64.161.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
24
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

573 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • CatProxies
  • Decodo
  • EZProxies
  • FastProxy
  • FloppyData
  • Geonode
  • IPFly
  • InfiniteProxies
  • Kookey
  • LemonBright
  • Novada
  • Proxio
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.64.0.0/14
since May 2005
AS5432Residential6,284
359 always on
Proximus NV

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
87.64.0.0/14262,144BE-BELGACOM-20050519Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PAMay 19, 2005abuse@proximus.com
└ 87.64.160.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PAAug 18, 2006abuse@proximus.com
via BE-BELGACOM-20050519

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

Covering aggregate above, the prefix's own history below

87.64.0.0/16

Routing history

Pattern
Stable
First seen
Sep 2011
Current origin since
Oct 2022 · 4.0 yr
Origin networks
1