Network · data from 2026-11-12
AS18311 CNCITY-AS-KR-KR - CNCITY energy CO.,LTD
Registry name: CNCITY-AS-KR-KR - CNCITY energy CO.,LTD, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18311, 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.
| 118.128.142.128/25 | No ROA | None | 16 2%low visibility |
| 121.184.101.128/25 | No ROA | None | 16 2%low visibility |
AS-SET
AS18311 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 41 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced37
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 118.128.142.128/25 | No ROA covers it. Add a ROA for AS18311, maxLength 25. |
| Route object: none | 118.128.142.128/25 | No route object for it. Add a route object with origin AS18311 in the RIR database for the space. |
| ROA: none | 121.184.101.128/25 | No ROA covers it. Add a ROA for AS18311, maxLength 25. |
| Route object: none | 121.184.101.128/25 | No route object for it. Add a route object with origin AS18311 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18311 whose prefix no peer sees AS18311 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.41.176.0/21 | RADB | No ROA |
| 61.41.184.0/22 | RADB | No ROA |
| 61.41.188.0/23 | RADB | No ROA |
| 61.252.176.0/23 | RADB | No ROA |
| 61.252.178.0/24 | RADB | No ROA |
| 210.122.74.0/24 | RADB | No ROA |
| 210.122.84.0/24 | RADB | No ROA |
| 210.122.86.0/23 | RADB | No ROA |
| 210.122.86.0/24 | RADB | No ROA |
| 210.122.87.0/24 | RADB | No ROA |
| 210.122.94.0/24 | RADB | No ROA |
| 210.122.117.0/24 | RADB | No ROA |
| 210.122.186.0/23 | RADB | No ROA |
| 210.122.186.0/24 | RADB | No ROA |
| 210.122.187.0/24 | RADB | No ROA |
| 210.122.191.0/24 | RADB | No ROA |
| 210.126.136.0/24 | RADB | No ROA |
| 210.126.141.0/24 | RADB | No ROA |
| 210.126.152.0/24 | RADB | No ROA |
| 210.126.155.0/24 | RADB | No ROA |
| 210.126.168.0/24 | RADB | No ROA |
| 210.126.187.0/24 | RADB | No ROA |
| 210.126.193.0/24 | RADB | No ROA |
| 210.126.196.0/24 | RADB | No ROA |
| 210.126.198.0/24 | RADB | No ROA |
| 210.126.204.0/24 | RADB | No ROA |
| 210.126.215.0/24 | RADB | No ROA |
| 211.210.50.0/23 | RADB | No ROA |
| 211.210.52.0/23 | RADB | No ROA |
| 211.210.54.0/24 | RADB | No ROA |
| 211.210.55.0/24 | RADB | No ROA |
| 211.210.56.0/23 | RADB | No ROA |
| 211.214.113.0/24 | RADB | No ROA |
| 211.214.114.0/23 | RADB | No ROA |
| 218.55.221.0/24 | RADB | No ROA |
| 218.55.222.0/24 | RADB | No ROA |
| 218.236.188.0/23 | RADB | 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.