Network · data from 2026-11-12
AS397575 ASCENSION-TECHNOLOGIES - Ascension Technologies
Registry name: ASCENSION-TECHNOLOGIES - Ascension Technologies, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS397575, 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.
| 64.29.240.0/20 | No ROA | RIR databaseARIN | 673 100% |
| 198.186.64.0/18 | No ROA | RIR databaseARIN | 673 100% |
| 199.4.216.0/23 | No ROA | RIR databaseARIN | 673 100% |
| 199.47.16.0/20 | No ROA | RIR databaseARIN | 673 100% |
| 199.250.64.0/18 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS397575 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 12 are in fix.csv.
- ROA: none5
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.29.240.0/20 | No ROA covers it. Add a ROA for AS397575, maxLength 20. |
| ROA: none | 198.186.64.0/18 | No ROA covers it. Add a ROA for AS397575, maxLength 18. |
| ROA: none | 199.4.216.0/23 | No ROA covers it. Add a ROA for AS397575, maxLength 23. |
| ROA: none | 199.47.16.0/20 | No ROA covers it. Add a ROA for AS397575, maxLength 20. |
| ROA: none | 199.250.64.0/18 | No ROA covers it. Add a ROA for AS397575, maxLength 18. |
Route objects not announced
Route objects with origin AS397575 whose prefix no peer sees AS397575 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.189.104.0/24 | ARIN | No ROA |
| 192.206.56.0/24 | ARIN | No ROA |
| 198.23.32.0/20 | ARIN | No ROA |
| 198.184.142.0/24 | ARIN | No ROA |
| 204.61.207.0/24 | ARIN | No ROA |
| 204.80.212.0/24 | ARIN | No ROA |
| 2620:1b4::/32 | 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.