Data as of Nov 20, 2026

81.245.35.0/24

5 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
32
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

2.1K observations

Proxy providers listing exits

  • BlurPath
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • LemonBright
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.244.0.0/14
since May 2005
AS5432Residential5,878
243 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.245.32.0/212,048BE-BELGACOM-ADSL1unknownASSIGNED PAMay 18, 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.245.0.0/16

Routing history

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