MANDARIN-ORIENTAL-MUNICH-FRANKFURT-NET
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 3 blocks across 2 clusters |
| Cluster ID | 205760656 |
| 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 | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 91.26.162.112/29 | MANDARIN-ORIENTAL-MUNICH-FRANKFURT-NET | RIPE | ASSIGNED PA | ● low |
| 2003:102:982a::/48 | MANDARIN-ORIENTAL-MUNICH-FRANKFURT-NET | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MANDARIN ORIENTAL MUNICH” — 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.
- MANDARIN_ORIENTAL_MUNICH_GMBH-NET 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.
- MANDARINORIENTALMUNICH-MUENCHEN-NET via Deutsche Telekom AG sub-allocation
- MANDARIN_ORIENTAL_MUNICH_GMBH-NET via M-net Telekommunikations GmbH sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
No discrepancies found among checked blocks.
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE