XINXIN-NETBAR

BGP inherited
Cluster stats
Netblocks8
All fragments 10 blocks across 3 clusters
Cluster ID209713536
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 16 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names 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
218.1.105.96/30 XINXIN-NETBAR APNIC ASSIGNED NON-PORTABLE ● high
61.167.26.96/27 XINXIN-NETBAR APNIC ASSIGNED NON-PORTABLE ● low
61.167.97.160/27 XINXIN-NETBAR APNIC ASSIGNED NON-PORTABLE ● low
61.180.144.192/28 XINXIN-NETBAR APNIC ASSIGNED NON-PORTABLE ● low
113.204.4.60/30 xinxin-netbar APNIC ASSIGNED NON-PORTABLE ● low
123.146.224.44/30 xinxin-netbar APNIC ASSIGNED NON-PORTABLE ● low
183.65.253.12/30 XinXin-NetBar APNIC ALLOCATED NON-PORTABLE ● low
221.10.5.96/30 Xinxin-Netbar APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “XINXIN 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: 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

AC2530-AP BG63-AP BG63-AP MAINT-CHINANET-CQ MAINT-CHINANET-SH MAINT-CNCGROUP-CQ MAINT-CNCGROUP-HL MAINT-CNCGROUP-SC MX379-AP MX379-AP XX288-AP XX288-AP +4 more