JM-DATA Telekom GmbH

GLEIF verified
LEI
529900BKQTG4MMCH8F63
Registered name
JM-DATA Telekom GmbH
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks5
All fragments 6 blocks across 2 clusters
Cluster ID206112167
RegistryPEERINGDB
Owner jurisdictionAT
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 529900BKQTG4MMCH8F63
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
193.203.0.196/32 JM-DATA Telekom GmbH PEERINGDB ASSIGNED ● high
193.203.0.247/32 JM-DATA Telekom GmbH PEERINGDB ASSIGNED ● high
2001:7f8:30:0:2:1:2:5447/128 JM-DATA Telekom GmbH PEERINGDB ASSIGNED ● high
2001:7f8:30:0:2:2:2:5447/128 JM-DATA Telekom GmbH PEERINGDB ASSIGNED ● high
2a03:4e40::/32 JM-DATA-Telekom-GmbH RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “JM DATA Telekom GmbH” — 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.
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.

Network trust

what's this?
RPKI hygiene: D how networks compare →
20.0% of checked blocks have valid RPKI ROA coverage (1 of 5)
No discrepancies found among checked blocks.

NIC Handles

AS25447 DUMY-RIPE DUMY-RIPE JM-DATA-MNT JNOC1-RIPE