Technische Universitaet Muenchen
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 2 · 256 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:4ca0:108::/48) |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 214529923 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 138.246.253.0/24 | Technische Universitaet Muenchen | RIPE | LEGACY | ● high |
| 2001:4ca0:108::/48 | Technische Universitaet Muenchen | RIPE | ASSIGNED | ● high |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:4ca0:108::/48 |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
Possible discrepancies (1)
These blocks are registered to Technische Universitaet Muenchen 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:4ca0:108::/48 /48 | authorized for AS12816 — Leibniz-Rechenzentrum |
NIC Handles
DUMY-RIPE
DUMY-RIPE
LRZ-MNT
ORG-TUM2-RIPE