CONGRESS-HOTEL-DRESDEN-NET

Data as of 2026-08-23
BGP inherited
Cluster stats
Netblocks6
IPv6 3 prefixes (largest 2003:c2:7030::/48)
All fragments 12 blocks across 3 clusters
Cluster ID227152399
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

2 weekly snapshots · JSON
6 0 netblocks since 2026-08-16
2026-08-16 peak 6 2026-08-23

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.155.175.240/29 CONGRESS-HOTEL-DRESDEN-NET RIPE ASSIGNED PA ● low
87.130.81.24/29 CONGRESS-HOTEL-DRESDEN-NET RIPE ASSIGNED PA ● low
87.190.4.176/28 CONGRESS-HOTEL-DRESDEN-NET RIPE ASSIGNED PA ● low
2003:c2:7030::/48 CONGRESS-HOTEL-DRESDEN-NET RIPE ASSIGNED ● low
2003:e7:1819::/48 CONGRESS-HOTEL-DRESDEN-NET RIPE ASSIGNED ● low
2003:e7:181d::/48 CONGRESS-HOTEL-DRESDEN-NET RIPE ASSIGNED ● low

IPv6 ranges (3)

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