bgpreport

Network · data from 2026-11-12

AS32024 BLUEFI-AS-1 - Blueficity

Registry name: BLUEFI-AS-1 - Blueficity, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS32024, 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.
38.86.96.0/23 No ROA None 673 100% 67
154.37.248.0/21 No ROA Other origin only 673 100% 67
154.50.97.0/24 No ROA None 673 100% 67
38.83.134.0/24 No ROA None 672 100% 67
38.79.32.0/24 No ROA RIR databaseARIN 670 100% 67
66.92.55.0/24 Valid RIR databaseARIN, RADB 673 100% 67
66.92.60.0/24 Valid RIR databaseARIN, RADB 673 100% 67
104.129.241.0/24 Valid RIR databaseARIN, RADB 671 100% 67
2607:69c0::/34 Valid RIR databaseARIN 636 100% 67
2607:69c0:4000::/34 Valid RIR databaseARIN, RADB 636 100% 68
2607:69c0:7fff::/48 Valid RIR databaseARIN 636 100% 68
2607:69c0:8000::/34 Valid RIR databaseARIN 636 100% 67
2607:69c0:c000::/34 Valid RIR databaseARIN 636 100% 68

AS-SET

AS32024 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 9 are in fix.csv.

  • ROA: none5
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none38.86.96.0/23No ROA covers it. Add a ROA for AS32024, maxLength 23.673 of 673
Route object: none38.86.96.0/23No route object for it. Add a route object with origin AS32024 in the RIR database for the space.673 of 673
ROA: none154.37.248.0/21No ROA covers it. Add a ROA for AS32024, maxLength 21.673 of 673
Route object: none154.37.248.0/21Route objects for it name AS27408. Add a route object with origin AS32024 in the RIR database for the space.673 of 673
ROA: none154.50.97.0/24No ROA covers it. Add a ROA for AS32024, maxLength 24.673 of 673
Route object: none154.50.97.0/24No route object for it. Add a route object with origin AS32024 in the RIR database for the space.673 of 673
ROA: none38.83.134.0/24No ROA covers it. Add a ROA for AS32024, maxLength 24.672 of 673
Route object: none38.83.134.0/24No route object for it. Add a route object with origin AS32024 in the RIR database for the space.672 of 673
ROA: none38.79.32.0/24No ROA covers it. Add a ROA for AS32024, maxLength 24.670 of 673

Route objects not announced

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