bgpreport

Network · data from 2026-11-12

AS30038 Andrena

Registry name: ANDRENA - Andrena, Inc., US · PeeringDB

8IPv4 routes 0.0% RPKI valid · 75.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No 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 AS30038, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30038, 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.80.186.0/24 No ROA None 672 100% 67
38.89.69.0/24 No ROA None 672 100% 67
38.108.105.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.106.64.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.123.158.0/24 No ROA Other IRR onlyBBOI 671 100% 67
38.96.182.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.106.77.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.96.183.0/24 No ROA Other IRR onlyRADB 667 99% 68

AS-SET

AS30038'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 18 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.80.186.0/24No ROA covers it. Add a ROA for AS30038, maxLength 24.672 of 673
Route object: none38.80.186.0/24No route object for it. Add a route object with origin AS30038 in the RIR database for the space.672 of 673
ROA: none38.89.69.0/24No ROA covers it. Add a ROA for AS30038, maxLength 24.672 of 673
Route object: none38.89.69.0/24No route object for it. Add a route object with origin AS30038 in the RIR database for the space.672 of 673
ROA: none38.108.105.0/24No ROA covers it. Add a ROA for AS30038, maxLength 24.672 of 673
Route object: RIR38.108.105.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.106.64.0/24No ROA covers it. Add a ROA for AS30038, maxLength 24.671 of 673
Route object: RIR38.106.64.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.123.158.0/24No ROA covers it. Add a ROA for AS30038, maxLength 24.671 of 673
Route object: RIR38.123.158.0/24Route object only in BBOI. Add it in the RIR database for the space.671 of 673
ROA: none38.96.182.0/24No ROA covers it. Add a ROA for AS30038, maxLength 24.670 of 673
Route object: RIR38.96.182.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.106.77.0/24No ROA covers it. Add a ROA for AS30038, maxLength 24.670 of 673
Route object: RIR38.106.77.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.96.183.0/24No ROA covers it. Add a ROA for AS30038, maxLength 24.667 of 673
Route object: RIR38.96.183.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

69.63.160.0/20ALTDBNo ROA
2001:470:343::/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.