KU Leuven
KULEUVEN
Registry
Cluster stats
| Netblocks | 9 · 3,002 IPv4 addresses |
| All fragments | 14 blocks across 6 clusters |
| Cluster ID | 208827281 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
9
0 netblocks since 2026-07-05
2026-07-05
peak 9
2026-07-19
IP Ranges (9)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.190.45.0 – 193.190.46.255 | KULeuven | RIPE | ASSIGNED PA | ● high |
| 193.190.145.128/26 | KULEUVEN | RIPE | ASSIGNED PA | ● high |
| 193.190.168.0/23 | KULEUVEN | RIPE | ASSIGNED PA | ● high |
| 193.190.176.0 – 193.190.181.255 | KULEUVEN | RIPE | ASSIGNED PA | ● high |
| 193.190.253.0/24 | KULEUVEN | RIPE | ASSIGNED PA | ● high |
| 193.190.255.0/25 | KULEUVEN | RIPE | ASSIGNED PA | ● high |
| 2001:6a8:2900::/48 | KULEUVEN | RIPE | ASSIGNED | ● high |
| 2001:6a8:2940::/48 | KULEUVEN | RIPE | ASSIGNED | ● high |
| 2001:6a8:2960::/48 | KULEUVEN | RIPE | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “KULEUVEN” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- KULEUVEN-S 1 blocks
- KULEUVEN-A 1 blocks
- KULEUVEN-B 1 blocks
- KULEUVEN-I 1 blocks
- KULEUVEN-X 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- KULEUVEN-S sub-allocation
- KULEUVEN-A sub-allocation
- KULEUVEN-B sub-allocation
- KULEUVEN-I sub-allocation
- KULEUVEN-X sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(9 of 9)
Possible discrepancies (7)
These blocks are registered to KU Leuven but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2001:6a8:2900::/48 /48 | authorized for AS2611 — BELNET |
| 2001:6a8:2940::/48 /48 | authorized for AS2611 — BELNET |
| 2001:6a8:2960::/48 /48 | authorized for AS2611 — BELNET |
| 193.190.176.0 – 193.190.181.255 /21 | authorized for AS2611 — BELNET |
| 193.190.168.0/23 /23 | authorized for AS2611 — BELNET |
| 193.190.45.0 – 193.190.46.255 /23 | authorized for AS2611 — BELNET |
| 193.190.253.0/24 /24 | authorized for AS2611 — BELNET |
NIC Handles
BELNET-MNT
DUMY-RIPE
DUMY-RIPE
KAC56-RIPE