bgpreport

Network · data from 2026-11-12

AS401779 AAROBAND

Registry name: AAROBAND - AaroBand, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401779, 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:f57f::/36 No ROA Other IRR onlyRADB 635 100% 68
66.93.48.0/24 Valid Other IRR onlyRADB 671 100% 67

AS-SET

AS401779's PeeringDB record names no 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: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none2602:f57f::/36No ROA covers it. Add a ROA for AS401779, maxLength 36.635 of 636
Route object: RIR2602:f57f::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR66.93.48.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS401779 is announced.

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.