SXZX

BGP inherited
Cluster stats
Netblocks6
All fragments 8 blocks across 2 clusters
Cluster ID206396280
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 15 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
124.75.29.0/29 SXZX APNIC ASSIGNED NON-PORTABLE ● high
124.75.29.16/28 SXZX APNIC ASSIGNED NON-PORTABLE ● high
124.75.29.32/28 SXZX APNIC ASSIGNED NON-PORTABLE ● high
124.75.29.48/28 SXZX APNIC ASSIGNED NON-PORTABLE ● high
218.83.165.0/27 SXZX APNIC ASSIGNED NON-PORTABLE ● high
202.99.222.0/28 SXZX APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SXZX” — 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.
  • LSXZXX via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP MAINT-CHINANET-SH MAINT-CNCGROUP-SX SW75-AP SW75-AP YG124-AP YG124-AP YG168-AP YG168-AP YG210-AP YG210-AP YG230-AP +3 more