Network · data from 2026-11-12
AS18144 AS-ENECOM - Enecom,Inc.
Registry name: AS-ENECOM - Enecom,Inc., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18144, 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.
| 1.0.64.0/18 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 27.133.176.0/21 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 58.183.0.0/16 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 61.195.8.0/21 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 61.205.32.0/21 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 110.74.224.0/21 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 116.81.0.0/16 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 121.200.128.0/18 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 202.7.112.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 202.208.112.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 203.168.64.0/18 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 219.105.48.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 219.118.224.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 220.210.224.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 221.12.192.0/18 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 222.231.64.0/18 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 36.52.136.0/21 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 36.52.152.0/21 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 36.52.160.0/21 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 36.53.232.0/21 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 223.223.0.0/17 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 103.205.168.0/22 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 2402:bc00::/29 | Valid | Other IRR onlyJPIRR, RADB | 634 100% |
AS-SET
AS18144 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 26 are in fix.csv.
- Route object: RIR23
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 1.0.64.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 27.133.176.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 58.183.0.0/16 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.195.8.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.205.32.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 110.74.224.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.81.0.0/16 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.200.128.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.7.112.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.208.112.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.168.64.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.105.48.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.118.224.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 220.210.224.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 221.12.192.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 222.231.64.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 36.52.136.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 36.52.152.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 36.52.160.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 36.53.232.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.223.0.0/17 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.205.168.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2402:bc00::/29 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18144 whose prefix no peer sees AS18144 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.183.0.0/17 | JPIRR | Invalid: maxLength |
| 58.183.128.0/17 | JPIRR | Invalid: maxLength |
| 202.236.14.0/23 | JPIRR, 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.