XINYU-NETBAR

BGP inherited
Cluster stats
Netblocks10
All fragments 14 blocks across 3 clusters
Cluster ID210152086
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 26 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
219.129.74.240/28 XINYU-NETBAR APNIC ASSIGNED NON-PORTABLE ● high
222.66.27.212/30 XINYU-NETBAR APNIC ASSIGNED NON-PORTABLE ● high
61.180.131.0/27 XINYU-NETBAR APNIC ASSIGNED NON-PORTABLE ● low
61.181.74.32/30 XinYu-netbar APNIC ASSIGNED NON-PORTABLE ● low
61.181.144.148/30 xinyu-netbar APNIC ASSIGNED NON-PORTABLE ● low
123.139.244.36/30 xinyu_NETBAR APNIC ASSIGNED NON-PORTABLE ● low
123.146.224.108/30 xinyu-netbar APNIC ASSIGNED NON-PORTABLE ● low
124.162.23.168/29 xinyu-netbar APNIC ASSIGNED NON-PORTABLE ● low
220.249.89.68/30 XinYu-Netbar APNIC ASSIGNED NON-PORTABLE ● low
221.10.159.230 – 221.10.159.233 XinYu-Netbar APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “XINYU 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: B how networks compare →
90.0% of checked blocks have valid RPKI ROA coverage (9 of 10)
No discrepancies found among checked blocks.

NIC Handles

AC937-AP AC937-AP BG63-AP BG63-AP CH679-AP CH679-AP CJ57-AP CJ57-AP DL878-AP DL878-AP HL1135-AP HL1135-AP +14 more