Network · data from 2026-11-12
AS401293 AS401293 - FSTcloud
Registry name: AS401293 - FSTcloud, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS401293, 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.
| 134.202.233.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 185.202.46.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 160.21.145.0/24 | Valid | RIR databaseRADB, RIPE | 667 99% |
| 2a09:340::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:140::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a11:2a80::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:3c00::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a10:dfc0::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:22c0::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:9a80::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:efc0::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:5040::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:f600::/29 | Valid | RIR databaseRIPE | 631 99% |
| 2a11:8580::/29 | Valid | RIR databaseRIPE | 629 99% |
| 2a11:a900::/29 | Valid | RIR databaseRIPE | 629 99% |
| 2a12:e600::/29 | Valid | RIR databaseRIPE | 629 99% |
AS-SET
AS401293 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 10 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 134.202.233.0/24 | ROAs covering it name AS834, not AS401293. If AS401293 should announce it, add a ROA for AS401293. |
| Route object: none | 134.202.233.0/24 | Route objects for it name AS834. Add a route object with origin AS401293 in the RIR database for the space. |
| ROA: origin | 185.202.46.0/24 | ROAs covering it name AS152606, not AS401293. If AS401293 should announce it, add a ROA for AS401293. |
| Route object: none | 185.202.46.0/24 | Route objects for it name AS152606. Add a route object with origin AS401293 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS401293 whose prefix no peer sees AS401293 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 134.202.17.0/24 | ARIN | Valid |
| 191.44.101.0/24 | RADB, RIPE | Valid |
| 2a0e:c180::/29 | RIPE | Valid |
| 2a0f:32c0::/29 | RIPE | Valid |
| 2a11:8380::/29 | RIPE | Valid |
| 2a12:9880::/29 | RIPE | 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.