NANJING-CUSTOMS

BGP inherited
Cluster stats
Netblocks8
All fragments 9 blocks across 2 clusters
Cluster ID208872033
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name 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
58.213.142.192/28 NANJING-CUSTOMS APNIC ASSIGNED NON-PORTABLE ● high
61.132.52.208/28 NANJING-CUSTOMS APNIC ASSIGNED NON-PORTABLE ● high
218.2.112.208/29 NANJING-CUSTOMS APNIC ASSIGNED NON-PORTABLE ● high
218.2.112.216/29 NANJING-CUSTOMS APNIC ASSIGNED NON-PORTABLE ● high
218.94.73.40/29 NANJING-CUSTOMS APNIC ASSIGNED NON-PORTABLE ● high
218.94.73.56/29 NANJING-CUSTOMS APNIC ASSIGNED NON-PORTABLE ● high
218.94.73.240/28 NANJING-CUSTOMS APNIC ASSIGNED NON-PORTABLE ● high
218.94.131.48/29 NANJING-CUSTOMS APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “NANJING CUSTOMS” — 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 →
87.5% of checked blocks have valid RPKI ROA coverage (7 of 8)
No discrepancies found among checked blocks.

NIC Handles

CH481-AP MAINT-CHINANET-JS MAINT-CHINANET-JS-NJ RYQ2-AP XS22-AP YB120-AP YB277-AP YR57-AP YR58-AP YR79-AP ZS251-AP