MELBOURNE-CUST-PERF

BGP inherited
Cluster stats
Netblocks6
All fragments 1,267 blocks across 506 clusters
Cluster ID204690542
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

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
37.128.184.176/29 MELBOURNE-CUST-PERF RIPE ASSIGNED PA ● low
37.128.189.240/28 MELBOURNE-CUST-PERF RIPE ASSIGNED PA ● low
46.20.226.152/29 MELBOURNE-CUST-PERF RIPE ASSIGNED PA ● low
46.20.230.32/29 MELBOURNE-CUST-PERF RIPE ASSIGNED PA ● low
46.20.238.64/29 MELBOURNE-CUST-PERF RIPE ASSIGNED PA ● low
188.65.179.72/29 MELBOURNE-CUST-PERF RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MELBOURNE CUST” — 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.
Combined view of all 506 name-family clusters →
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.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-MELBOURNE