TCC-STUTTGART-NET

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks9
IPv6 3 prefixes (largest 2003:102:14::/48)
Record ID247824552
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 (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.153.94.128/27 TCC-STUTTGART-NET RIPE ASSIGNED PA ● low
62.153.239.0/29 TCC-STUTTGART-NET RIPE ASSIGNED PA ● low
62.225.114.8/29 TCC-STUTTGART-NET RIPE ASSIGNED PA ● low
91.26.90.8/29 TCC-STUTTGART-NET RIPE ASSIGNED PA ● low
195.243.183.48/28 TCC-STUTTGART-NET RIPE ASSIGNED PA ● low
217.7.11.240/29 TCC-STUTTGART-NET RIPE ASSIGNED PA ● low
2003:41:c02a::/48 TCC-STUTTGART-NET RIPE ASSIGNED ● low
2003:102:14::/48 TCC-STUTTGART-NET RIPE ASSIGNED ● low
2003:102:1b::/48 TCC-STUTTGART-NET RIPE ASSIGNED ● low

IPv6 ranges (3)

Footprint over time

15 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-10-04

Network trust

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

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE