bgpreport

Network · data from 2026-11-12

AS32001 HYPHA-1 - Hypha Worker Co-operative Inc.

Registry name: HYPHA-1 - Hypha Worker Co-operative Inc., CA · not in PeeringDB

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

Announced routes

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

140.235.158.0/24 No ROA Nonecovered by 140.235.158.0/23 673 100% 67
140.235.159.0/24 No ROA Nonecovered by 140.235.158.0/23 673 100% 67
2602:2a0::/48 No ROA Nonecovered by 2602:2a0::/40 634 100% 68
2602:2a0:1::/48 No ROA Nonecovered by 2602:2a0::/40 634 100% 68

AS-SET

AS32001 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 11 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none140.235.158.0/24No ROA covers it. Add a ROA for AS32001, maxLength 24.673 of 673
Route object: none140.235.158.0/24No route object for it. A route object for 140.235.158.0/23 with origin AS32001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32001 in the RIR database for the space.673 of 673
ROA: none140.235.159.0/24No ROA covers it. Add a ROA for AS32001, maxLength 24.673 of 673
Route object: none140.235.159.0/24No route object for it. A route object for 140.235.158.0/23 with origin AS32001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32001 in the RIR database for the space.673 of 673
ROA: none2602:2a0::/48No ROA covers it. Add a ROA for AS32001, maxLength 48.634 of 636
Route object: none2602:2a0::/48No route object for it. A route object for 2602:2a0::/40 with origin AS32001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32001 in the RIR database for the space.634 of 636
ROA: none2602:2a0:1::/48No ROA covers it. Add a ROA for AS32001, maxLength 48.634 of 636
Route object: none2602:2a0:1::/48No route object for it. A route object for 2602:2a0::/40 with origin AS32001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32001 in the RIR database for the space.634 of 636

Route objects not announced

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

65.254.3.0/24RADBNo ROA
140.235.158.0/23RADBNo ROA
2602:2a0::/40RADBNo 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.