bgpreport

Network · data from 2026-11-12

AS403056 SHUTTLEAI - ShuttleAI,

Registry name: SHUTTLEAI - ShuttleAI,, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS403056, 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.
2602:f2bb:95::/48 Invalid: maxLength RIR databaseARIN 9 1%low visibility 11

AS-SET

AS403056 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 3 are in fix.csv.

  • ROA: maxLength1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength2602:f2bb:95::/48ROA 2602:f2bb::/40 AS403056 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2602:f2bb:95::/48.9 of 636

Route objects not announced

Route objects with origin AS403056 whose prefix no peer sees AS403056 announce. Many are kept on purpose (backup routes, space announced only in some places).

23.165.236.0/24ARINValid
2602:f2bb::/40ARINValid

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.