bgpreport

Network · data from 2026-11-12

AS401416 AURA-AS - Aurascape, Inc.

Registry name: AURA-AS - Aurascape, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401416, 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.
74.123.9.0/24 Valid Other IRR onlyRADB 673 100% 66
162.212.228.0/24 Valid Other IRR onlyRADB 673 100% 69
162.212.229.0/24 Valid Other IRR onlyRADB 673 100% 69
162.212.230.0/24 Valid Other IRR onlyRADB 673 100% 68
162.212.231.0/24 Valid Other IRR onlyRADB 673 100% 68
74.123.8.0/24 Valid Other IRR onlyRADB 672 100% 67
74.123.10.0/24 Valid Other IRR onlyRADB 672 100% 67
74.123.11.0/24 Valid Other IRR onlyRADB 672 100% 67
2607:dd40:1700::/40 Valid Other IRR onlyRADB 636 100% 69
2607:dd40:1f00::/40 Valid Other IRR onlyRADB 635 100% 68
169.155.42.0/24 Valid RIR databaseARIN, RADB 673 100% 66

AS-SET

AS401416 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 15 are in fix.csv.

  • Route object: RIR10
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR74.123.9.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.212.228.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.212.229.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.212.230.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.212.231.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR74.123.8.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.123.10.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.123.11.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2607:dd40:1700::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2607:dd40:1f00::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

74.123.8.0/22ARINValid
162.212.228.0/22ARINValid
2607:dd40::/32ARINValid
2607:dd40:1800::/40RADBValid
2607:dd40:1c00::/40RADBValid

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.