WILHELM-LAYHER-GUEGLINGEN-NET

BGP inherited
Cluster stats
Netblocks6
All fragments 10 blocks across 3 clusters
Cluster ID209013086
RegistryRIPE
Customersfind 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

Footprint over time

5 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
80.150.190.0/26 WILHELM-LAYHER-GUEGLINGEN-NET RIPE ASSIGNED PA ● low
91.26.241.200/29 WILHELM-LAYHER-GUEGLINGEN-NET RIPE ASSIGNED PA ● low
194.25.170.192/28 WILHELM-LAYHER-GUEGLINGEN-NET RIPE ASSIGNED PA ● low
217.5.133.64/27 WILHELM-LAYHER-GUEGLINGEN-NET RIPE ASSIGNED PA ● low
2003:c9:6827::/48 WILHELM-LAYHER-GUEGLINGEN-NET RIPE ASSIGNED ● low
2003:102:6024::/48 WILHELM-LAYHER-GUEGLINGEN-NET RIPE ASSIGNED ● low

Possibly related to this organisation

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

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

DTAG-NIC DUMY-RIPE DUMY-RIPE