No.31, Jin-rong Street
SUZHOU-CS-TRAFFIC-BUREAU
BGP inherited
Cluster stats
| Netblocks | 8 |
| All fragments | 15 blocks across 7 clusters |
| Cluster ID | 206411675 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 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
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-13
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 218.4.147.8/29 | SUZHOU-CS-TRAFFIC-BUREAU | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.4.203.160/29 | SUZHOU-CS-TRAFFIC-BUREAU | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.4.203.192/29 | SUZHOU-CS-TRAFFIC-BUREAU | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.4.203.200/29 | SUZHOU-CS-TRAFFIC-BUREAU | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.4.203.208/29 | SUZHOU-CS-TRAFFIC-BUREAU | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.4.203.216/29 | SUZHOU-CS-TRAFFIC-BUREAU | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.4.203.224/29 | SUZHOU-CS-TRAFFIC-BUREAU | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.4.203.232/29 | SUZHOU-CS-TRAFFIC-BUREAU | APNIC | ASSIGNED NON-PORTABLE | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “SUZHOU CS TRAFFIC” — 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.
- SUZHOU-CS-TRAFFIC-MANAGE-BUREAU 2 blocks
- SUZHOU-CS-TRAFFIC-DESIGN-COMM 1 blocks
- SUZHOU-CS-TRAFFIC-GOV 1 blocks
- SUZHOU-CS-TRAFFIC-POLICE-STATION 1 blocks
- SUZHOU-CS-TRAFFIC-DESIGN-CORP 1 blocks
- SUZHOU-CS-TRAFFIC-POLICE-DEPT 1 blocks
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.
- SUZHOU-TC-TRAFFIC-BUREAU via No.31,Jin-rong Street sub-allocation
- SUZHOU-CS-TRAFFIC-DESIGN-CORP via No.31,Jin-rong Street sub-allocation
- SUZHOU-CS-TRAFFIC-POLICE-DEPT via No.31,Jin-rong Street sub-allocation
- suzhou-TAICANG-TRAFFIC-BANK via No.31,Jin-rong Street sub-allocation
- suzhou-GONGGONG-TRAFFIC-CORP via No.31,Jin-rong Street sub-allocation
- suzhou-SUZHOU-TC-TRAFFIC-GROUP-CORP via No.31,Jin-rong Street sub-allocation
- suzhou-XIAN-TRAFFIC-UNIV via No.31,Jin-rong Street sub-allocation
- suzhou-zjg-traffic-gove via No.31,Jin-rong Street sub-allocation
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
CH446-AP
CH446-AP
MAINT-CHINANET-JS-SZ
MY33-AP
ZJ12-AP