bgpreport

Network · data from 2026-11-12

AS200665 hfestenergi Hammerfest Energi Bredbaand AS

Registry name: hfestenergi Hammerfest Energi Bredbaand AS, NO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200665, 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.
2a0a:9b80::/32 No ROA None 3 0%low visibility 3
2a0a:9c80::/32 No ROA None 3 0%low visibility 3
141.195.8.0/21 Valid RIR databaseRIPE 673 100% 67
185.97.196.0/22 Valid RIR databaseRIPE 673 100% 67
185.135.134.0/23 Valid RIR databaseRIPE 673 100% 67
185.154.16.0/22 Valid RIR databaseRIPE 673 100% 67
185.180.232.0/22 Valid RIR databaseRIPE 673 100% 67
185.181.80.0/22 Valid RIR databaseRIPE 673 100% 67
2.58.27.0/24 Valid RIR databaseRIPE 670 100% 67
176.124.60.0/22 Valid RIR databaseRIPE 669 99% 67
176.125.244.0/22 Valid RIR databaseRIPE 669 99% 67
2a06:700::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS200665 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 4 are in fix.csv.

  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none2a0a:9b80::/32No ROA covers it. Add a ROA for AS200665, maxLength 32.3 of 636
Route object: none2a0a:9b80::/32No route object for it. Add a route object with origin AS200665 in the RIR database for the space.3 of 636
ROA: none2a0a:9c80::/32No ROA covers it. Add a ROA for AS200665, maxLength 32.3 of 636
Route object: none2a0a:9c80::/32No route object for it. Add a route object with origin AS200665 in the RIR database for the space.3 of 636

Route objects not announced

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