Network · data from 2026-11-12
AS19940 ACECAPE-INC - Ace Innovative Networks, Inc.
Registry name: ACECAPE-INC - Ace Innovative Networks, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19940, 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.
| 199.89.147.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 66.114.72.0/24 | Valid | RIR databaseARIN | 673 100% |
| 66.114.73.0/24 | Valid | RIR databaseARIN | 673 100% |
| 66.114.76.0/24 | Valid | RIR databaseARIN | 673 100% |
| 66.114.87.0/24 | Valid | RIR databaseARIN | 673 100% |
| 72.0.224.0/24 | Valid | RIR databaseARIN | 672 100% |
| 72.0.225.0/24 | Valid | RIR databaseARIN | 672 100% |
| 72.0.227.0/24 | Valid | RIR databaseARIN | 672 100% |
| 72.0.232.0/24 | Valid | RIR databaseARIN | 672 100% |
| 72.0.239.0/24 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS19940 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 6 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.89.147.0/24 | No ROA covers it. Add a ROA for AS19940, maxLength 24. |
| Route object: RIR | 199.89.147.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19940 whose prefix no peer sees AS19940 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.114.64.0/19 | ARIN, NTTCOM | Valid |
| 72.0.224.0/20 | ARIN, NTTCOM | Valid |
| 216.16.144.0/20 | ARIN, NTTCOM | Valid |
| 2606:8800::/32 | ARIN, NTTCOM | 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.