MTU-FRIEDRICHSHAFEN-AUGSBURG-NET
BGP inherited
Cluster stats
| Netblocks | 6 |
| All fragments | 36 blocks across 12 clusters |
| Cluster ID | 205594263 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
3 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-12
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 87.128.174.88/29 | MTU-FRIEDRICHSHAFEN-AUGSBURG-NET | RIPE | ASSIGNED PA | ● low |
| 91.24.68.144/28 | MTU-FRIEDRICHSHAFEN-AUGSBURG-NET | RIPE | ASSIGNED PA | ● low |
| 91.26.159.96/29 | MTU-FRIEDRICHSHAFEN-AUGSBURG-NET | RIPE | ASSIGNED PA | ● low |
| 2003:c3:e81f::/48 | MTU-FRIEDRICHSHAFEN-AUGSBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:d4:4822::/48 | MTU-FRIEDRICHSHAFEN-AUGSBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:ef:2026::/48 | MTU-FRIEDRICHSHAFEN-AUGSBURG-NET | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MTU FRIEDRICHSHAFEN” — 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.
- MTU-FRIEDRICHSHAFEN-NET 6 blocks
- MTU-FRIEDRICHSHAFEN-MAGDEBURG-NET 4 blocks
- MTU-FRIEDRICHSHAFEN-RUHSTORF-A-D-ROTT-NET 4 blocks
- MTU-FRIEDRICHSHAFEN-ESCHBORN-NET 2 blocks
- MTU-FRIEDRICHSHAFEN-OBERURSEL-NET 2 blocks
- MTU-FRIEDRICHSHAFEN-UEBERLINGEN-NET 2 blocks
- MTU-FRIEDRICHSHAFEN-DUISBURG-NET 2 blocks
- MTU-FRIEDRICHSHAFEN-RUHSTORF-AN-DER-ROTT-NET 2 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.
- FlughafenFriedrichshafenGmbH_vDC-IPv4_NET via TeleData GmbH sub-allocation
- Zf Friedrichshafen Ag via COLT Technology Services Group Limited sub-allocation
- Zf Friedrichshafen Ag via COLT Technology Services Group Limited sub-allocation
- Zf Friedrichshafen Ag via COLT Technology Services Group Limited sub-allocation
- Zf Friedrichshafen Ag via COLT Technology Services Group Limited sub-allocation
- Zf Friedrichshafen Ag via COLT Technology Services Group Limited sub-allocation
- Interhyp V6 Friedrichshafen sub-allocation
- FlughafenFriedrichshafenGmbH_vDC-IPv6_NET via TeleData GmbH sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
No discrepancies found among checked blocks.
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE