PRO-HWY-AT

BGP inherited
Cluster stats
Netblocks8
Cluster ID208981301
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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.120.246.172/30 PRO-HWY-AT RIPE ASSIGNED PA ● low
80.121.217.176/30 PRO-HWY-AT RIPE ASSIGNED PA ● low
80.122.95.220/30 PRO-HWY-AT RIPE ASSIGNED PA ● low
80.122.200.12/30 PRO-HWY-AT RIPE ASSIGNED PA ● low
80.122.200.24/30 PRO-HWY-AT RIPE ASSIGNED PA ● low
80.122.201.40/30 PRO-HWY-AT RIPE ASSIGNED PA ● low
80.122.201.140/30 PRO-HWY-AT RIPE ASSIGNED PA ● low
80.123.132.96/30 PRO-HWY-AT RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS8447-MNT DUMY-RIPE DUMY-RIPE