Data as of Nov 11, 2026

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

Exits seen per day

33 observations

Proxy providers listing exits

  • Ake.net
  • Byteful
  • CatProxies
  • CoreProxy
  • DataImpulse
  • FastProxy
  • FlashProxy
  • GeekProxy
  • Geonode
  • IPOasis
  • IPPeak
  • IPRoyal
  • InfiniteProxies
  • LemonBright
  • PSBProxy
  • PacketStream
  • Proxies.fo
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • SpyderProxy
  • VibeProxies

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.65.80.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.65.0.0/16

Routing history

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