Network · data from 2026-11-12
AS18117 NTT Communications ICT Solutions
Registry name: NTTIP-AS-AP - NTT Australia Solutions Pty Ltd, AU · PeeringDB
12IPv4 routes
41.7% RPKI valid · 83.3% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
7No ROA
2 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
67Route objects not announced
registered with origin AS18117, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS18117, 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.
| 210.87.19.0/24 | No ROA | Other origin only | 667 99% |
| 103.112.188.0/24 | No ROA | None | 629 93% |
| 203.111.46.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 203.111.102.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 203.111.104.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 210.87.25.0/24 | No ROA | Other IRR onlyRADB | 667 99% |
| 210.87.32.0/24 | No ROA | Other IRR onlyRADB | 667 99% |
| 118.127.80.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 118.127.64.0/19 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 118.127.65.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 668 99% |
| 118.127.86.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 118.127.89.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
AS-SET
AS18117's PeeringDB record names no 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 81 are in fix.csv.
- ROA: none7
- Route object: none2
- Route object: RIR5
- Route object: not announced67
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 210.87.19.0/24 | No ROA covers it. Add a ROA for AS18117, maxLength 24. |
| Route object: none | 210.87.19.0/24 | Route objects for it name AS17819. Add a route object with origin AS18117 in the RIR database for the space. |
| ROA: none | 103.112.188.0/24 | No ROA covers it. Add a ROA for AS18117, maxLength 24. |
| Route object: none | 103.112.188.0/24 | No route object for it. Add a route object with origin AS18117 in the RIR database for the space. |
| ROA: none | 203.111.46.0/24 | No ROA covers it. Add a ROA for AS18117, maxLength 24. |
| Route object: RIR | 203.111.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.111.102.0/24 | No ROA covers it. Add a ROA for AS18117, maxLength 24. |
| Route object: RIR | 203.111.102.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.111.104.0/24 | No ROA covers it. Add a ROA for AS18117, maxLength 24. |
| Route object: RIR | 203.111.104.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.87.25.0/24 | No ROA covers it. Add a ROA for AS18117, maxLength 24. |
| Route object: RIR | 210.87.25.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.87.32.0/24 | No ROA covers it. Add a ROA for AS18117, maxLength 24. |
| Route object: RIR | 210.87.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18117 whose prefix no peer sees AS18117 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 118.127.64.0/20 | APNIC | Valid |
| 118.127.64.0/21 | APNIC | Valid |
| 118.127.64.0/22 | APNIC | Valid |
| 118.127.64.0/23 | APNIC | Valid |
| 118.127.64.0/24 | APNIC, NTTCOM | Valid |
| 118.127.66.0/23 | APNIC | Valid |
| 118.127.66.0/24 | APNIC, NTTCOM | Valid |
| 118.127.67.0/24 | APNIC | Valid |
| 118.127.68.0/22 | APNIC | Valid |
| 118.127.68.0/23 | APNIC | Valid |
| 118.127.68.0/24 | APNIC, NTTCOM | Valid |
| 118.127.69.0/24 | APNIC, NTTCOM | Valid |
| 118.127.70.0/23 | APNIC | Valid |
| 118.127.70.0/24 | APNIC, NTTCOM | Valid |
| 118.127.71.0/24 | APNIC, NTTCOM | Valid |
| 118.127.72.0/21 | APNIC | Valid |
| 118.127.72.0/22 | APNIC | Valid |
| 118.127.72.0/23 | APNIC | Valid |
| 118.127.72.0/24 | APNIC, NTTCOM | Valid |
| 118.127.73.0/24 | APNIC, NTTCOM | Valid |
| 118.127.74.0/23 | APNIC | Valid |
| 118.127.74.0/24 | APNIC, NTTCOM | Valid |
| 118.127.74.88/30 | APNIC | Invalid: maxLength |
| 118.127.75.0/24 | APNIC, NTTCOM | Valid |
| 118.127.76.0/22 | APNIC | Valid |
| 118.127.76.0/23 | APNIC | Valid |
| 118.127.76.0/24 | APNIC, NTTCOM | Valid |
| 118.127.77.0/24 | APNIC, NTTCOM | Valid |
| 118.127.78.0/23 | APNIC, NTTCOM | Valid |
| 118.127.78.0/24 | APNIC, NTTCOM | Valid |
| 118.127.79.0/24 | APNIC, NTTCOM | Valid |
| 118.127.80.0/20 | APNIC | Valid |
| 118.127.80.0/21 | APNIC | Valid |
| 118.127.80.0/23 | APNIC | Valid |
| 118.127.80.0/24 | APNIC, NTTCOM | Valid |
| 118.127.81.0/24 | APNIC, NTTCOM | Valid |
| 118.127.82.0/23 | APNIC | Valid |
| 118.127.82.0/24 | APNIC, NTTCOM | Valid |
| 118.127.83.0/24 | APNIC, NTTCOM | Valid |
| 118.127.84.0/22 | APNIC | Valid |
| 118.127.84.0/23 | APNIC | Valid |
| 118.127.84.0/24 | APNIC, NTTCOM | Valid |
| 118.127.85.0/24 | APNIC, NTTCOM | Valid |
| 118.127.86.0/23 | APNIC | Valid |
| 118.127.87.0/24 | APNIC, NTTCOM | Valid |
| 118.127.88.0/21 | APNIC | Valid |
| 118.127.88.0/22 | APNIC | Valid |
| 118.127.88.0/23 | APNIC | Valid |
| 118.127.88.0/24 | APNIC, NTTCOM | Valid |
| 118.127.90.0/23 | APNIC | Valid |
| 118.127.90.0/24 | APNIC, NTTCOM | Valid |
| 118.127.91.0/24 | APNIC, NTTCOM | Valid |
| 118.127.92.0/22 | APNIC | Valid |
| 118.127.92.0/23 | APNIC, RADB | Valid |
| 118.127.92.0/24 | APNIC, NTTCOM, RADB | Valid |
| 118.127.93.0/24 | APNIC, NTTCOM | Valid |
| 118.127.94.0/23 | APNIC | Valid |
| 118.127.94.0/24 | APNIC, NTTCOM | Valid |
| 118.127.95.0/24 | APNIC, NTTCOM | Valid |
| 203.18.148.0/24 | NTTCOM | No ROA |
| 203.19.79.0/24 | NTTCOM | No ROA |
| 203.26.4.0/24 | NTTCOM | No ROA |
| 203.27.76.0/24 | NTTCOM | No ROA |
| 203.31.213.0/24 | NTTCOM | No ROA |
| 203.56.250.0/24 | NTTCOM | No ROA |
| 203.63.219.0/24 | NTTCOM | No ROA |
| 210.8.91.0/24 | NTTCOM | 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.