bgpreport

Network · data from 2026-11-12

AS216374 HardangerBreiband Hardanger Breiband AS

Registry name: HardangerBreiband Hardanger Breiband AS, NO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS216374, 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.
83.242.0.0/19 No ROA RIR databaseRIPE 673 100% 66
84.205.32.0/19 No ROA RIR databaseRIPE 673 100% 66
91.123.32.0/20 No ROA RIR databaseRIPE 673 100% 66
185.83.16.0/22 No ROA RIR databaseRIPE 673 100% 66
185.221.0.0/22 No ROA RIR databaseRIPE 673 100% 66
2a02:cc40::/29 No ROA RIR databaseRIPE 633 100% 67

AS-SET

AS216374 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: none6
ChangePrefix or setDetailFull-table peers
ROA: none83.242.0.0/19No ROA covers it. Add a ROA for AS216374, maxLength 19.673 of 673
ROA: none84.205.32.0/19No ROA covers it. Add a ROA for AS216374, maxLength 19.673 of 673
ROA: none91.123.32.0/20No ROA covers it. Add a ROA for AS216374, maxLength 20.673 of 673
ROA: none185.83.16.0/22No ROA covers it. Add a ROA for AS216374, maxLength 22.673 of 673
ROA: none185.221.0.0/22No ROA covers it. Add a ROA for AS216374, maxLength 22.673 of 673
ROA: none2a02:cc40::/29No ROA covers it. Add a ROA for AS216374, maxLength 29.633 of 636

Route objects not announced

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