MELBOURNE-CUST-XBIT

BGP inherited
Cluster stats
Netblocks8
All fragments 1,267 blocks across 506 clusters
Cluster ID209902804
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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.159.224.136/29 MELBOURNE-CUST-XBIT RIPE ASSIGNED PA ● low
5.159.225.48/29 MELBOURNE-CUST-XBIT RIPE ASSIGNED PA ● low
5.159.225.72/29 MELBOURNE-CUST-XBIT RIPE ASSIGNED PA ● low
5.159.227.8/29 MELBOURNE-CUST-XBIT RIPE ASSIGNED PA ● low
37.128.185.144/29 MELBOURNE-CUST-XBIT RIPE ASSIGNED PA ● low
46.20.228.72/29 MELBOURNE-CUST-XBIT RIPE ASSIGNED PA ● low
46.20.229.40/29 MELBOURNE-CUST-XBIT RIPE ASSIGNED PA ● low
188.65.179.32/29 MELBOURNE-CUST-XBIT 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