Data as of Nov 6, 2026
213.181.32.0/19
18 residential-proxy exits · 30 daysProximus NV
Residential-proxy exits
Proxy exits
18
0.22% of its addresses · 30 days
Always-on exits
2
11% of its exits
Spread
8 of 32
/24s with at least one exit
Providers
41
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
3.4K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 213.181.56.0/24 | 1 | 5 | |
| 213.181.38.0/24 | 1 | 1 | |
| 213.181.39.0/24 | 0 | 3 | |
| 213.181.48.0/24 | 0 | 3 | |
| 213.181.46.0/24 | 0 | 2 | |
| 213.181.47.0/24 | 0 | 1 | |
| 213.181.51.0/24 | 0 | 1 | |
| 213.181.59.0/24 | 0 | 1 |
Proxy providers listing exits
- 711Proxy
- Ake.net
- AnyIP
- B2Proxy
- BottingTools
- Bright Data
- BuyingProxy
- Byteful
- DataImpulse
- Decodo
- Evomi
- FastProxy
- FlashProxy
- FloppyData
- GeekProxy
- IPFly
- IPPeak
- InfiniteProxies
- KindProxy
- LemonBright
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PrivateByte
- Proxmint
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- Q2IP
- RainProxy
- RapidProxy
- ResiProxies
- RolaProxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- VitalExclusive
- Webshare
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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 213.181.32.0/19 | 8,192 | BE-BELGACOM-20010119 | Proximus NV (ORG-BA4-RIPE) · BE | ALLOCATED PA | — | abuse@ |
| └ 213.181.33.0/24 | 256 | BGC-HOSTING-33 | Belgacom Hosting 33 | ASSIGNED PA | Jun 10, 2004 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.34.0/23 | 512 | BE-RRN | Used by the "national registry of natural persons" of Belgium | ASSIGNED PA | Feb 5, 2008 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.36.0/24 | 256 | BGC-HOSTING-36 | Belgacom Hosting 36 | ASSIGNED PA | Mar 27, 2003 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.37.0/24 | 256 | BE-PUBLILINK | Belgacom Publilink 37 | ASSIGNED PA | Feb 5, 2008 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.38.0/24 | 256 | MSS-sfwgstr7 | Fortigate | ASSIGNED PA | Aug 24, 2010 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.39.0/24 | 256 | MSS-sfwgstr5 | Fortigate | ASSIGNED PA | Oct 13, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.40.0/29 | 8 | PXSSPEAR-1 | Proximus SpearIT 1 | ASSIGNED PA | May 26, 2021 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.41.0/24 | 256 | BGC-HOSTING-41 | Belgacom Hosting 41 | ASSIGNED PA | Feb 5, 2008 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.44.0/23 | 512 | BELGACOM-CORP-2 | Belgacom Corporate Network | ASSIGNED PA | Jul 23, 2003 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.46.0/24 | 256 | MSS-sfwgstr6 | Fortigate | ASSIGNED PA | Feb 3, 2010 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.47.0/24 | 256 | MSS-sfwgstr4 | Fortigate | ASSIGNED PA | Jul 6, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.48.0/24 | 256 | MSS-sfwgstr1 | Fortigate | ASSIGNED PA | Jul 6, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.49.0/24 | 256 | MSS-sfwgstr2 | Fortigate | ASSIGNED PA | Jul 6, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.50.0/24 | 256 | MSS-sfwgstr1 | Fortigate | ASSIGNED PA | Jul 6, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.52.0/24 | 256 | BGC-HOSTING-52 | Belgacom Hosting 52 | ASSIGNED PA | Jul 6, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.53.0/24 | 256 | BGC-HOSTING-53 | Belgacom Hosting 53 | ASSIGNED PA | Jul 6, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.54.0/24 | 256 | BGC-HOSTING-54 | Belgacom Hosting 54 | ASSIGNED PA | Jul 6, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.55.0/24 | 256 | BGC-HOSTING-55 | Belgacom Hosting 55 | ASSIGNED PA | Jul 6, 2009 | abuse@ via BE-BELGACOM-20010119 |
| └ 213.181.60.0/22 | 1,024 | BMB-GPRS-UMTS-PHASE-1 | Belgacom Mobile, GPRS & UMTS | ASSIGNED PA | Sep 23, 2003 | abuse@ 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
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 5,368 | 66% | 6 | |
| Hosting | 1,792 | 22% | 7 | |
| Mobile | 1,024 | 13% | 1 | |
| Business | 8 | 0.10% | 1 |
Network & registry
Origin network
AS5432
BE
- Name
- Proximus NV
- Type
- Internet provider
- Registered
- Oct 23, 1995
- Domain
- proximus.com
- Website
- www.proximus.com/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
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
Whois
Registration for this announcement
- Range
- 213.
181. 32. 0/ 19 - Netname
- BE-BELGACOM-20010119
- Registrant
- Proximus NV
- Registrant country
- BE
- Organization
- Proximus NV (ORG-BA4-RIPE)
- Org country
- BE
- Type
- ALLOCATED PA
- Created
- Not stated by the registry
- Updated
- Feb 7, 2025
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- BE
- Delegated
- Jan 19, 2001
- Status
- assigned
Report abuse
Abuse contact
- abuse@
proximus. com - Name
- Proximus Internet Anti-Fraude Center
- Handle
- BIAC1-RIPE