WUXI-traffic-bureau

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8
All fragments 14 blocks across 5 clusters
Cluster ID217138091
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.160.69.152/29 WUXI-TRAFFIC-BUREAU APNIC ASSIGNED NON-PORTABLE ● high
58.215.242.88/30 WUXI-traffic-bureau APNIC ASSIGNED NON-PORTABLE ● low
61.160.74.204/30 WUXI-traffic-bureau APNIC ASSIGNED NON-PORTABLE ● low
61.177.117.40/30 WUXI-traffic-bureau APNIC ASSIGNED NON-PORTABLE ● low
61.177.122.4/30 WUXI-traffic-bureau APNIC ASSIGNED NON-PORTABLE ● low
61.177.123.8/30 WUXI-traffic-bureau APNIC ASSIGNED NON-PORTABLE ● low
218.90.162.16/29 wuxi-traffic-bureau APNIC ASSIGNED NON-PORTABLE ● low
222.191.248.0/28 WUXI-traffic-bureau APNIC ASSIGNED NON-PORTABLE ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
62.5% of checked blocks have valid RPKI ROA coverage (5 of 8)
No discrepancies found among checked blocks.

NIC Handles

CH456-AP CH456-AP MAINT-CHINANET-JS YG351-AP