Network · data from 2026-11-12
AS58536 AP-CONAC-AS-AP - CONAC (China Organizational Name Administration Center)
Registry name: AP-CONAC-AS-AP - CONAC (China Organizational Name Administration Center), CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58536, 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.
| 111.235.169.0/24 | No ROA | None | 673 100% |
| 111.235.162.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 111.235.163.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 111.235.164.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 111.235.165.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 111.235.173.0/24 | No ROA | Other IRR onlyRADB | 546 81% |
| 111.235.172.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 523 78% |
| 111.235.168.0/24 | No ROA | Other IRR onlyNTTCOM | 2 0%low visibility |
| 2401:b400:8::/48 | No ROA | RIR databaseAPNIC | 634 100% |
| 2401:b400:9::/48 | No ROA | RIR databaseAPNIC | 634 100% |
| 2401:b400:11::/48 | No ROA | RIR databaseAPNIC | 634 100% |
AS-SET
AS58536 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 23 are in fix.csv.
- ROA: none11
- Route object: none1
- Route object: RIR7
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 111.235.169.0/24 | No ROA covers it. Add a ROA for AS58536, maxLength 24. |
| Route object: none | 111.235.169.0/24 | No route object for it. Add a route object with origin AS58536 in the RIR database for the space. |
| ROA: none | 111.235.162.0/24 | No ROA covers it. Add a ROA for AS58536, maxLength 24. |
| Route object: RIR | 111.235.162.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 111.235.163.0/24 | No ROA covers it. Add a ROA for AS58536, maxLength 24. |
| Route object: RIR | 111.235.163.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 111.235.164.0/24 | No ROA covers it. Add a ROA for AS58536, maxLength 24. |
| Route object: RIR | 111.235.164.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 111.235.165.0/24 | No ROA covers it. Add a ROA for AS58536, maxLength 24. |
| Route object: RIR | 111.235.165.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 111.235.173.0/24 | No ROA covers it. Add a ROA for AS58536, maxLength 24. |
| Route object: RIR | 111.235.173.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 111.235.172.0/24 | No ROA covers it. Add a ROA for AS58536, maxLength 24. |
| Route object: RIR | 111.235.172.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 111.235.168.0/24 | No ROA covers it. Add a ROA for AS58536, maxLength 24. |
| Route object: RIR | 111.235.168.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 2401:b400:8::/48 | No ROA covers it. Add a ROA for AS58536, maxLength 48. |
| ROA: none | 2401:b400:9::/48 | No ROA covers it. Add a ROA for AS58536, maxLength 48. |
| ROA: none | 2401:b400:11::/48 | No ROA covers it. Add a ROA for AS58536, maxLength 48. |
Route objects not announced
Route objects with origin AS58536 whose prefix no peer sees AS58536 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 111.235.174.0/24 | NTTCOM, RADB | No ROA |
| 2401:b400::/48 | APNIC | No ROA |
| 2401:b400:1::/48 | APNIC | No ROA |
| 2401:b400:2::/48 | APNIC | No ROA |
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.