taipingyangbaoxian

Registry
Cluster stats
Netblocks8 · 277 IPv4 addresses
All fragments 9 blocks across 2 clusters
Cluster ID210182487
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 10 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
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
112.64.184.28/30 taipingyangbaoxian APNIC ASSIGNED NON-PORTABLE ● low
112.64.184.32/30 taipingyangbaoxian APNIC ASSIGNED NON-PORTABLE ● low
112.64.184.36/30 taipingyangbaoxian APNIC ASSIGNED NON-PORTABLE ● low
112.64.185.0/25 taipingyangbaoxian APNIC ASSIGNED NON-PORTABLE ● low
112.64.185.128/26 taipingyangbaoxian APNIC ASSIGNED NON-PORTABLE ● low
112.64.185.192/26 taipingyangbaoxian APNIC ASSIGNED NON-PORTABLE ● low
122.191.3.144/28 TAIPINGYANGBAOXIAN APNIC ASSIGNED NON-PORTABLE ● low
219.149.28.164/32 TaiPingYangBaoXian APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AC1718-AP CC1699-AP CC1699-AP JZ1175-AP JZ1175-AP MAINT-CHINANET-LN MAINT-CNCGROUP-HB MAINT-CNCGROUP-SH YR194-AP YR194-AP