bgpreport

Network · data from 2026-11-12

AS401293 AS401293 - FSTcloud

Registry name: AS401293 - FSTcloud, US · not in PeeringDB

3IPv4 routes 33.3% RPKI valid · 33.3% with a route object
13IPv6 routes 100.0% RPKI valid · 100.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
0No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS401293, seen from no peer

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 2
185.202.46.0/24 Invalid: origin Other origin only 1 0%low visibility 1
160.21.145.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
2a09:340::/29 Valid RIR databaseRIPE 634 100% 67
2a0f:140::/29 Valid RIR databaseRIPE 634 100% 67
2a11:2a80::/29 Valid RIR databaseRIPE 633 100% 67
2a10:3c00::/29 Valid RIR databaseRIPE 632 99% 67
2a10:dfc0::/29 Valid RIR databaseRIPE 632 99% 67
2a11:22c0::/29 Valid RIR databaseRIPE 632 99% 67
2a11:9a80::/29 Valid RIR databaseRIPE 632 99% 67
2a11:efc0::/29 Valid RIR databaseRIPE 632 99% 67
2a13:5040::/29 Valid RIR databaseRIPE 632 99% 67
2a11:f600::/29 Valid RIR databaseRIPE 631 99% 67
2a11:8580::/29 Valid RIR databaseRIPE 629 99% 67
2a11:a900::/29 Valid RIR databaseRIPE 629 99% 67
2a12:e600::/29 Valid RIR databaseRIPE 629 99% 67

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
ChangePrefix or setDetailFull-table peers
ROA: origin134.202.233.0/24ROAs covering it name AS834, not AS401293. If AS401293 should announce it, add a ROA for AS401293.2 of 673
Route object: none134.202.233.0/24Route objects for it name AS834. Add a route object with origin AS401293 in the RIR database for the space.2 of 673
ROA: origin185.202.46.0/24ROAs covering it name AS152606, not AS401293. If AS401293 should announce it, add a ROA for AS401293.1 of 673
Route object: none185.202.46.0/24Route objects for it name AS152606. Add a route object with origin AS401293 in the RIR database for the space.1 of 673

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/24ARINValid
191.44.101.0/24RADB, RIPEValid
2a0e:c180::/29RIPEValid
2a0f:32c0::/29RIPEValid
2a11:8380::/29RIPEValid
2a12:9880::/29RIPEValid

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.