bgpreport

Network · data from 2026-11-12

AS3923 FAA-MMAC - Federal Aviation Administration

Registry name: FAA-MMAC - Federal Aviation Administration, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3923, 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.

2606:7ec0:1903::/48 No ROA Nonecovered by 2606:7ec0::/32 635 100% 69
152.123.8.0/21 No ROA Other IRR onlyRADB 670 100% 69
152.123.16.0/24 No ROA Other IRR onlyRADB 670 100% 69
162.58.0.0/16 No ROA Other IRR onlyRADB 670 100% 69
2001:19e8:8041::/48 No ROA Other IRR onlyRADB 635 100% 70
152.123.16.0/23 No ROA Other IRR onlyRADB 377 56% 67

AS-SET

AS3923 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2606:7ec0:1903::/48No ROA covers it. Add a ROA for AS3923, maxLength 48.635 of 636
Route object: none2606:7ec0:1903::/48No route object for it. A route object for 2606:7ec0::/32 with origin AS3923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3923 in the RIR database for the space.635 of 636
ROA: none152.123.8.0/21No ROA covers it. Add a ROA for AS3923, maxLength 21.670 of 673
Route object: RIR152.123.8.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none152.123.16.0/24No ROA covers it. Add a ROA for AS3923, maxLength 24.670 of 673
Route object: RIR152.123.16.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none162.58.0.0/16No ROA covers it. Add a ROA for AS3923, maxLength 16.670 of 673
Route object: RIR162.58.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2001:19e8:8041::/48No ROA covers it. Add a ROA for AS3923, maxLength 48.635 of 636
Route object: RIR2001:19e8:8041::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none152.123.16.0/23No ROA covers it. Add a ROA for AS3923, maxLength 23.377 of 673
Route object: RIR152.123.16.0/23Route object only in RADB. Add it in the RIR database for the space.377 of 673

Route objects not announced

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

2606:7ec0::/32RADBNo ROA

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.