Data as of Nov 19, 2026

81.169.0.0/17

30 residential-proxy exits · 30 days

Proximus NV

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
94% of it

Residential-proxy exits

Proxy exits
30
0.09% of its addresses · 30 days
Spread
21 of 128
/24s with at least one exit
Providers
17
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

491 observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • EnigmaProxy
  • FastProxy
  • IPFly
  • IPMUSK
  • KocerRoxy
  • LemonBright
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • Proxiware
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • ThunderProxy
  • VantageProxies

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.169.0.0/1732,768BE-BELGACOM-20030410Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PAApr 10, 2003abuse@proximus.com
└ 81.169.0.0/212,048BE-PROXIMUS-MDEProximus Mobile InternetASSIGNED PAAug 5, 2003abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.8.0/212,048BE-PROXIMUS-MDEProximus Mobile InternetASSIGNED PASep 2, 2009abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.16.0/212,048BE-PROXIMUS-MDEProximus Mobile InternetASSIGNED PAAug 27, 2007abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.24.0/212,048BE-PROXIMUS-MDEProximus Mobile InternetASSIGNED PAAug 27, 2007abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.32.0/204,096BE-PROXIMUS-MDEProximus Mobile InternetASSIGNED PAFeb 17, 2005abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.48.0/212,048BE-PROXIMUS-MDEProximus Mobile InternetASSIGNED PANov 27, 2007abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.56.0 - 81.169.58.255768M2MInternetProximus Data Network InfrastructureASSIGNED PAJan 21, 2010abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.59.0/24256BE-PROXIMUS-NETWORKProximus infrastructureASSIGNED PADec 13, 2013abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.60.0/221,024BE-PROXIMUS-MIProximus Data Network InfrastructureASSIGNED PASep 10, 2003abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.64.0/204,096BE-PROXIMUS-MIProximus Mobile InternetASSIGNED PAMay 23, 2003abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.80.0/204,096BE-PROXIMUS-MI2Proximus Mobile Internet 2ASSIGNED PAMay 3, 2004abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.96.0/204,096BE-PROXIMUS-MI3Proximus Mobile Internet 3ASSIGNED PAFeb 10, 2005abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.112.0/221,024BE-PROXIMUS-MVNEProximus Mobile Internet MVNEASSIGNED PAAug 2, 2007abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.116.0 - 81.169.123.2552,048BE-PROXIMUS-MI7Proximus Mobile Internet 7ASSIGNED PANov 27, 2007abuse@proximus.com
via BE-BELGACOM-20030410
└ 81.169.124.0/221,024BE-PROXIMUS-MIProximus Data Network InfrastructureASSIGNED PAMay 23, 2003abuse@proximus.com
via BE-BELGACOM-20030410

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

32,768 addresses
TypeAddressesShareRanges
Mobile30,72094%113
Residential2,0486.3%2

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Dec 2015 · 11 yr
Origin networks
2
Last change of origin
Dec 2015
Recorded history

History

Handoffs
1