Data as of Nov 13, 2026

81.243.136.0/24

2 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
16
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

179 observations

Proxy providers listing exits

  • ByteProxies
  • Byteful
  • GSocks
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.240.0.0/14
since May 2005
AS5432Residential6,417
326 always on
Proximus NV

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.240.0.0/13524,288BE-BELGACOM-20021129Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PAOct 27, 2003abuse@proximus.com
└ 81.243.128.0/204,096BE-BELGACOM-ADSL1unknownASSIGNED PAMar 21, 2005abuse@proximus.com
via BE-BELGACOM-20021129

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

81.243.0.0/16

Routing history

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