Network · data from 2026-11-12
AS14297 ACI-WORLDWIDE - ACI Worldwide, Inc.
Registry name: ACI-WORLDWIDE - ACI Worldwide, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14297, 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.
| 65.198.80.0/22 | No ROA | Other IRR onlyALTDB | 673 100% |
| 65.222.196.0/22 | No ROA | Other IRR onlyALTDB | 673 100% |
| 138.229.4.0/22 | Valid | RIR databaseARIN | 673 100% |
| 138.229.12.0/23 | Valid | RIR databaseARIN | 673 100% |
| 138.229.14.0/24 | Valid | RIR databaseARIN | 673 100% |
| 139.131.18.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.28.0/23 | Valid | RIR databaseARIN | 673 100% |
| 139.131.42.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.76.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.80.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.96.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.108.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.112.0/23 | Valid | RIR databaseARIN | 673 100% |
| 139.131.114.0/23 | Valid | RIR databaseARIN | 673 100% |
| 139.131.120.0/23 | Valid | RIR databaseARIN | 673 100% |
| 139.131.122.0/23 | Valid | RIR databaseARIN | 673 100% |
| 139.131.126.0/23 | Valid | RIR databaseARIN | 673 100% |
| 139.131.134.0/23 | Valid | RIR databaseARIN | 673 100% |
| 139.131.143.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.160.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.164.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.174.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.180.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.182.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.184.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.192.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.193.0/24 | Valid | RIR databaseARIN | 673 100% |
| 139.131.194.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.208.0/20 | Valid | RIR databaseARIN | 673 100% |
| 139.131.224.0/20 | Valid | RIR databaseARIN | 673 100% |
| 139.131.240.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 139.131.240.0/24 | Valid | RIR databaseARIN | 673 100% |
| 185.147.172.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.147.174.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 199.189.232.0/23 | Valid | RIR databaseARIN | 673 100% |
| 199.189.234.0/23 | Valid | RIR databaseARIN | 673 100% |
| 206.201.24.0/23 | Valid | RIR databaseARIN | 673 100% |
| 206.201.26.0/23 | Valid | RIR databaseARIN | 673 100% |
| 206.201.28.0/24 | Valid | RIR databaseARIN | 673 100% |
| 206.201.30.0/24 | Valid | RIR databaseARIN, NTTCOM, RADB | 672 100% |
| 206.201.31.0/24 | Valid | RIR databaseARIN, NTTCOM | 672 100% |
| 206.201.16.0/23 | Valid | RIR databaseARIN | 671 100% |
| 138.229.15.0/24 | Valid | RIR databaseARIN | 670 100% |
| 206.201.18.0/23 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS14297 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 23 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 65.198.80.0/22 | No ROA covers it. Add a ROA for AS14297, maxLength 22. |
| Route object: RIR | 65.198.80.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 65.222.196.0/22 | No ROA covers it. Add a ROA for AS14297, maxLength 22. |
| Route object: RIR | 65.222.196.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14297 whose prefix no peer sees AS14297 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.229.0.0/20 | ARIN | No ROA |
| 139.131.0.0/16 | ARIN, RADB | No ROA |
| 139.131.12.0/23 | ARIN, RADB | Valid |
| 139.131.64.0/21 | ARIN, RADB | Valid |
| 139.131.64.0/24 | RADB | Valid |
| 139.131.66.0/23 | RADB | Valid |
| 139.131.88.0/24 | RADB | No ROA |
| 139.131.108.0/24 | ARIN | Valid |
| 139.131.196.0/23 | ARIN, RADB | Valid |
| 139.131.198.0/23 | ARIN, RADB | Valid |
| 139.131.200.0/23 | RADB | No ROA |
| 139.131.204.0/23 | RADB | Valid |
| 139.131.206.0/23 | RADB | Valid |
| 139.131.250.0/24 | ARIN, RADB | Valid |
| 185.147.172.0/22 | RIPE | No ROA |
| 206.201.16.0/22 | ARIN | No ROA |
| 206.201.24.0/22 | ARIN | No ROA |
| 206.201.29.0/24 | ARIN | Valid |
| 206.201.30.0/23 | ARIN | 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.