36.163.0.0/17
Currently announced by AS56046 CMNET-Jiangsu-AP, in the routed prefix 36.163.0.0/17.
- Current ASN
- AS56046
- CMNET-Jiangsu-AP
- Routed prefix
- 36.163.0.0/17
- Most specific route covering this prefix
- ASNs over time
- 2
- 2 announcement records
- RIR allocation
- APNIC
- China · 36.128.0.0/10
Routing data · Nov 8, 2026, 10:26 UTC
ASN historyEvery routed prefix covering 36.163.0.0/17
| Prefix | ASN | Name | Registered country | First seen (UTC) | Last seen (UTC) | Status |
|---|---|---|---|---|---|---|
| 36.163.0.0/17 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.128.0.0/10 | AS9808 | China Mobile Communications Group Co., Ltd. | Before monitoring | 2026-11-08 10:26 | Announcing |
More specific routes52 total
| Prefix | ASN | Name | Registered country | First seen (UTC) | Last seen (UTC) | Status |
|---|---|---|---|---|---|---|
| 36.163.0.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.4.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.8.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.12.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.16.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.20.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.24.0/21 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.24.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.26.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.27.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.28.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.29.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.30.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.31.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.32.0/21 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.33.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.35.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.36.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.38.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.39.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.40.0/21 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.40.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.42.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.44.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.48.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.52.0/23 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.54.0/23 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.56.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.56.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.57.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.58.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.59.0/24 | AS56046 | CMNET-Jiangsu-AP | 2026-11-05 18:22 | 2026-11-08 10:26 | Announcing | |
| 36.163.60.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.64.0/21 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.66.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.76.0/22 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.80.0/21 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.81.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.83.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.85.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.86.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.87.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.88.0/21 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.88.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.89.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.90.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.92.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.93.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.104.0/21 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.118.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.119.0/24 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing | |
| 36.163.120.0/21 | AS56046 | CMNET-Jiangsu-AP | Before monitoring | 2026-11-08 10:26 | Announcing |
Change logAll changes
The routes covering this address have had no origin changes since ASNBase started monitoring.