bgpreport

Network · data from 2026-11-12

AS54384 CORE-ASN - CORE Electric Cooperative

Registry name: CORE-ASN - CORE Electric Cooperative, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54384, 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.143.229.0/24 No ROA None 670 100% 67
38.143.233.0/24 No ROA None 667 99% 67
74.123.194.0/23 Valid RIR databaseARIN 671 100% 67

AS-SET

AS54384 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: none2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.143.229.0/24No ROA covers it. Add a ROA for AS54384, maxLength 24.670 of 673
Route object: none38.143.229.0/24No route object for it. Add a route object with origin AS54384 in the RIR database for the space.670 of 673
ROA: none38.143.233.0/24No ROA covers it. Add a ROA for AS54384, maxLength 24.667 of 673
Route object: none38.143.233.0/24No route object for it. Add a route object with origin AS54384 in the RIR database for the space.667 of 673

Route objects not announced

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

67.148.152.0/24RADBNo ROA
2001:470:655::/48ARINValid

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.