THOMANN-NET

BGP inherited
Cluster stats
Netblocks6 · 362 IPv4 addresses
All fragments 14 blocks across 4 clusters
Cluster ID209132245
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
212.114.130.56/29 THOMANN-NET RIPE ASSIGNED PA ● high
212.204.75.0/24 THOMANN-NET RIPE ASSIGNED PA ● high
212.204.112.192/26 THOMANN-NET RIPE ASSIGNED PA ● high
80.255.12.160/29 THOMANN RIPE ASSIGNED PA ● low
176.94.163.48/28 THOMANN-NET RIPE ASSIGNED PA ● low
212.144.24.80/28 THOMANN-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “THOMANN” — 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: 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

ARCOR-MNT CORE-BACKBONE DUMY-RIPE DUMY-RIPE MNET-MNT TAC64-RIPE