Network · data from 2026-11-12
AS24404 CNISP-UNION - CNISP-Union Technology (Beijing) Co., Ltd
Registry name: CNISP-UNION - CNISP-Union Technology (Beijing) Co., Ltd, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24404, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 163.53.60.0/24 | Invalid: origin | None | 28 4%low visibility |
| 103.249.244.0/24 | No ROA | Other origin only | 672 100% |
| 218.245.18.0/23 | Valid | None | 671 100% |
| 114.113.154.0/23 | Valid | Nonecovered by 114.113.152.0/22 | 5 1%low visibility |
| 116.90.84.0/23 | Valid | None | 5 1%low visibility |
| 116.90.86.0/23 | Valid | None | 5 1%low visibility |
| 121.52.222.0/23 | Valid | Nonecovered by 121.52.216.0/21 | 5 1%low visibility |
| 218.245.0.0/23 | Valid | Nonecovered by 218.245.0.0/22 | 5 1%low visibility |
AS-SET
AS24404 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 21 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none8
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 163.53.60.0/24 | ROAs covering it name AS4847, not AS24404. If AS24404 should announce it, add a ROA for AS24404. |
| Route object: none | 163.53.60.0/24 | No route object for it. Add a route object with origin AS24404 in the RIR database for the space. |
| ROA: none | 103.249.244.0/24 | No ROA covers it. Add a ROA for AS24404, maxLength 24. |
| Route object: none | 103.249.244.0/24 | Route objects for it name AS4847. Add a route object with origin AS24404 in the RIR database for the space. |
| Route object: none | 218.245.18.0/23 | No route object for it. Add a route object with origin AS24404 in the RIR database for the space. |
| Route object: none | 114.113.154.0/23 | No route object for it. A route object for 114.113.152.0/22 with origin AS24404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24404 in the RIR database for the space. |
| Route object: none | 116.90.84.0/23 | No route object for it. Add a route object with origin AS24404 in the RIR database for the space. |
| Route object: none | 116.90.86.0/23 | No route object for it. Add a route object with origin AS24404 in the RIR database for the space. |
| Route object: none | 121.52.222.0/23 | No route object for it. A route object for 121.52.216.0/21 with origin AS24404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24404 in the RIR database for the space. |
| Route object: none | 218.245.0.0/23 | No route object for it. A route object for 218.245.0.0/22 with origin AS24404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24404 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24404 whose prefix no peer sees AS24404 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 114.113.144.0/22 | NTTCOM, RADB | Valid |
| 114.113.148.0/22 | NTTCOM, RADB | Valid |
| 114.113.152.0/22 | NTTCOM, RADB | Valid |
| 114.113.156.0/22 | NTTCOM, RADB | Valid |
| 118.26.160.0/22 | NTTCOM, RADB | Valid |
| 118.26.164.0/22 | NTTCOM, RADB | Valid |
| 118.26.168.0/22 | NTTCOM, RADB | Valid |
| 118.26.172.0/22 | NTTCOM, RADB | Valid |
| 121.52.216.0/21 | NTTCOM, RADB | Valid |
| 218.245.0.0/22 | NTTCOM, RADB | Valid |
| 218.245.4.0/22 | NTTCOM, RADB | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.