Network · data from 2026-11-12
AS18362 NETWAY-AS-AP - Netway Communication Co.,Ltd.
Registry name: NETWAY-AS-AP - Netway Communication Co.,Ltd., TH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18362, 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.
| 203.78.96.0/20 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.78.96.0/21 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.78.98.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.78.110.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.78.111.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.78.104.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 203.78.109.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
AS-SET
AS18362 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 39 are in fix.csv.
- ROA: none7
- Route object: RIR7
- Route object: not announced25
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.78.96.0/20 | No ROA covers it. Add a ROA for AS18362, maxLength 20. |
| Route object: RIR | 203.78.96.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.78.96.0/21 | No ROA covers it. Add a ROA for AS18362, maxLength 21. |
| Route object: RIR | 203.78.96.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.78.98.0/24 | No ROA covers it. Add a ROA for AS18362, maxLength 24. |
| Route object: RIR | 203.78.98.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.78.110.0/24 | No ROA covers it. Add a ROA for AS18362, maxLength 24. |
| Route object: RIR | 203.78.110.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.78.111.0/24 | No ROA covers it. Add a ROA for AS18362, maxLength 24. |
| Route object: RIR | 203.78.111.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.78.104.0/22 | No ROA covers it. Add a ROA for AS18362, maxLength 22. |
| Route object: RIR | 203.78.104.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.78.109.0/24 | No ROA covers it. Add a ROA for AS18362, maxLength 24. |
| Route object: RIR | 203.78.109.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18362 whose prefix no peer sees AS18362 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.78.96.0/22 | NTTCOM, RADB | No ROA |
| 203.78.96.0/23 | NTTCOM, RADB | No ROA |
| 203.78.96.0/24 | NTTCOM, RADB | No ROA |
| 203.78.97.0/24 | NTTCOM, RADB | No ROA |
| 203.78.98.0/23 | NTTCOM, RADB | No ROA |
| 203.78.99.0/24 | NTTCOM, RADB | No ROA |
| 203.78.100.0/22 | NTTCOM, RADB | No ROA |
| 203.78.100.0/23 | NTTCOM, RADB | No ROA |
| 203.78.100.0/24 | NTTCOM, RADB | No ROA |
| 203.78.101.0/24 | NTTCOM, RADB | No ROA |
| 203.78.102.0/23 | NTTCOM, RADB | No ROA |
| 203.78.102.0/24 | NTTCOM, RADB | No ROA |
| 203.78.103.0/24 | NTTCOM, RADB | No ROA |
| 203.78.104.0/21 | NTTCOM, RADB | No ROA |
| 203.78.104.0/23 | NTTCOM, RADB | No ROA |
| 203.78.104.0/24 | NTTCOM, RADB | No ROA |
| 203.78.105.0/24 | NTTCOM, RADB | No ROA |
| 203.78.106.0/23 | NTTCOM, RADB | No ROA |
| 203.78.106.0/24 | NTTCOM, RADB | No ROA |
| 203.78.107.0/24 | NTTCOM, RADB | No ROA |
| 203.78.108.0/22 | NTTCOM, RADB | No ROA |
| 203.78.108.0/23 | NTTCOM, RADB | No ROA |
| 203.78.108.0/24 | NTTCOM, RADB | No ROA |
| 203.78.110.0/23 | NTTCOM, RADB | No ROA |
| 2401:8640::/32 | 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.