LANCOM-SYSTEMS-WUERSELEN-NET

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks6
IPv6 2 prefixes (largest 2003:43:a010::/48)
All fragments 14 blocks across 2 clusters
Cluster ID213634831
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 · report an issue

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.153.130.128/27 LANCOM-SYSTEMS-WUERSELEN-NET RIPE ASSIGNED PA ● low
62.157.227.112/28 LANCOM-SYSTEMS-WUERSELEN-NET RIPE ASSIGNED PA ● low
87.130.79.16/29 LANCOM-SYSTEMS-WUERSELEN-NET RIPE ASSIGNED PA ● low
217.6.21.88/29 LANCOM-SYSTEMS-WUERSELEN-NET RIPE ASSIGNED PA ● low
2003:43:a010::/48 LANCOM-SYSTEMS-WUERSELEN-NET RIPE ASSIGNED ● low
2003:e3:201d::/48 LANCOM-SYSTEMS-WUERSELEN-NET RIPE ASSIGNED ● low

IPv6 ranges (2)

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