Data as of Nov 20, 2026

81.244.252.0/23

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
0.59% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
22
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

208 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.244.253.0/2402
81.244.252.0/2401

Proxy providers listing exits

  • 2Extract
  • BirdProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • HASDATA
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • Shifter
  • VitalExclusive

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.244.252.0/23512BE-SKYNET-20011108Office NamurASSIGNED PAAug 7, 2006abuse@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.244.0.0/16

Routing history

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