bgpreport

Network · data from 2026-11-12

AS54021 FIXFLYER1 - FIX FLYER, LLC

Registry name: FIXFLYER1 - FIX FLYER, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54021, 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.201.134.0/24 Invalid: origin Other origin only 188 28% 54
162.217.102.0/24 No ROA Other IRR onlyRADB 673 100% 70
74.201.180.0/24 No ROA Other IRR onlyRADB 672 100% 70
66.150.102.0/24 Valid RIR databaseARIN 673 100% 66

AS-SET

AS54021 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 6 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: origin74.201.134.0/24ROAs covering it name AS13789, AS54201, not AS54021. If AS54021 should announce it, add a ROA for AS54021.188 of 673
Route object: none74.201.134.0/24Route objects for it name AS13789, AS54201. Add a route object with origin AS54021 in the RIR database for the space.188 of 673
ROA: none162.217.102.0/24No ROA covers it. Add a ROA for AS54021, maxLength 24.673 of 673
Route object: RIR162.217.102.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none74.201.180.0/24No ROA covers it. Add a ROA for AS54021, maxLength 24.672 of 673
Route object: RIR74.201.180.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS54021 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.