Data as of Nov 19, 2026

213.181.32.0/19

16 residential-proxy exits · 30 days

Proximus NV

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
66% of it

Residential-proxy exits

Proxy exits
16
0.20% of its addresses · 30 days
Always-on exits
1
6.3% of its exits
Spread
7 of 32
/24s with at least one exit
Providers
44
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

3.6K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • Ake.net
  • AnyIP
  • B2Proxy
  • BottingTools
  • Bright Data
  • BuyingProxy
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GeekProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LemonBright
  • NovaProxy
  • Novada
  • Oxylabs
  • PSBProxy
  • PrivateByte
  • Proxmint
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RolaProxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare
  • YumiProxy

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
213.181.32.0/198,192BE-BELGACOM-20010119Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PA—abuse@proximus.com
└ 213.181.33.0/24256BGC-HOSTING-33Belgacom Hosting 33ASSIGNED PAJun 10, 2004abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.34.0/23512BE-RRNUsed by the "national registry of natural persons" of BelgiumASSIGNED PAFeb 5, 2008abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.36.0/24256BGC-HOSTING-36Belgacom Hosting 36ASSIGNED PAMar 27, 2003abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.37.0/24256BE-PUBLILINKBelgacom Publilink 37ASSIGNED PAFeb 5, 2008abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.38.0/24256MSS-sfwgstr7FortigateASSIGNED PAAug 24, 2010abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.39.0/24256MSS-sfwgstr5FortigateASSIGNED PAOct 13, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.40.0/298PXSSPEAR-1Proximus SpearIT 1ASSIGNED PAMay 26, 2021abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.41.0/24256BGC-HOSTING-41Belgacom Hosting 41ASSIGNED PAFeb 5, 2008abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.44.0/23512BELGACOM-CORP-2Belgacom Corporate NetworkASSIGNED PAJul 23, 2003abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.46.0/24256MSS-sfwgstr6FortigateASSIGNED PAFeb 3, 2010abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.47.0/24256MSS-sfwgstr4FortigateASSIGNED PAJul 6, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.48.0/24256MSS-sfwgstr1FortigateASSIGNED PAJul 6, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.49.0/24256MSS-sfwgstr2FortigateASSIGNED PAJul 6, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.50.0/24256MSS-sfwgstr1FortigateASSIGNED PAJul 6, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.52.0/24256BGC-HOSTING-52Belgacom Hosting 52ASSIGNED PAJul 6, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.53.0/24256BGC-HOSTING-53Belgacom Hosting 53ASSIGNED PAJul 6, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.54.0/24256BGC-HOSTING-54Belgacom Hosting 54ASSIGNED PAJul 6, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.55.0/24256BGC-HOSTING-55Belgacom Hosting 55ASSIGNED PAJul 6, 2009abuse@proximus.com
via BE-BELGACOM-20010119
└ 213.181.60.0/221,024BMB-GPRS-UMTS-PHASE-1Belgacom Mobile, GPRS & UMTSASSIGNED PASep 23, 2003abuse@proximus.com
via BE-BELGACOM-20010119

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

8,192 addresses
TypeAddressesShareRanges
Residential5,36866%6
Hosting1,79222%7
Mobile1,02413%1
Business80.10%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jun 2005 · 21 yr
Origin networks
2
Last change of origin
Jun 2005
Recorded history

History

Handoffs
1