T-SYSTEMS-MUENCHEN-NET

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks8
IPv6 1 prefix (largest 2003:ff:5017::/48)
Also registered under this name 522 netblocks across 91 separate records
Record ID238619635
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.154.199.128/26 T-SYSTEMS-MUENCHEN-NET RIPE ASSIGNED PA ● low
62.154.234.192/27 T-SYSTEMS-MUENCHEN-NET RIPE ASSIGNED PA ● low
80.146.200.192/29 T-SYSTEMS-MUENCHEN-NET RIPE ASSIGNED PA ● low
80.148.31.64/28 T-SYSTEMS-MUENCHEN-NET RIPE ASSIGNED PA ● low
80.148.31.112/28 T-SYSTEMS-MUENCHEN-NET RIPE ASSIGNED PA ● low
91.24.95.64/27 T-SYSTEMS-MUENCHEN-NET RIPE ASSIGNED PA ● low
195.243.159.88/29 T-SYSTEMS-MUENCHEN-NET RIPE ASSIGNED PA ● low
2003:ff:5017::/48 T-SYSTEMS-MUENCHEN-NET RIPE ASSIGNED ● low

IPv6 ranges (1)

Footprint over time

11 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-09-06

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE