Data as of Nov 16, 2026

87.67.119.0/24

8 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
3
38% of its exits
Providers
37
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

3.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AnyIP
  • BottingTools
  • Byteful
  • CliProxy
  • Decodo
  • FastProxy
  • FloppyData
  • Geonode
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LudaxProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_BASIC
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.64.0.0/14
since May 2005
AS5432Residential6,621
298 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.67.96.0/198,192BE-BELGACOM-ADSL1unknownASSIGNED PASep 1, 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.67.0.0/16

Routing history

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