tianhe-netbar

Unresolved
Cluster stats
Netblocks6
All fragments 7 blocks across 2 clusters
Cluster ID210333479
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 15 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 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
219.129.19.176/28 TIANHE-NETBAR APNIC ASSIGNED NON-PORTABLE ● high
61.180.233.224/27 TIANHE-NETBAR APNIC ASSIGNED NON-PORTABLE ● low
113.204.26.224/29 tianhe-netbar APNIC ASSIGNED NON-PORTABLE ● low
123.146.224.60/30 tianhe-netbar APNIC ASSIGNED NON-PORTABLE ● low
218.106.24.64/26 tianhe-netbar APNIC ASSIGNED NON-PORTABLE ● low
220.249.91.64/30 Tianhe-netbar APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “tianhe netbar” — 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.
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: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (4 of 6)
No discrepancies found among checked blocks.

NIC Handles

BG63-AP BG63-AP DL878-AP DL878-AP MAINT-CHINANET-GD MAINT-CN-ZM28 MAINT-CNCGROUP-CQ MAINT-CNCGROUP-HB MAINT-CNCGROUP-HL MX379-AP MX379-AP TC254-AP +3 more