Data as of Nov 11, 2026

87.67.44.0/24

7 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
18
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

280 observations

Proxy providers listing exits

  • AnyIP
  • BottingTools
  • Byteful
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • Infatica
  • LemonBright
  • MangoProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • SPYDERPROXY_PREMIUM
  • ThunderProxy
  • VantageProxies
  • 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.67.0.0/1816,384BE-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.67.0.0/16

Routing history

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