bgpreport

Network · data from 2026-11-12

AS397602 BOREALIS-BROADBAND - BOREALIS BROADBAND INC.

Registry name: BOREALIS-BROADBAND - BOREALIS BROADBAND INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS397602, 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.
216.73.140.0/24 No ROA Nonecovered by 216.73.140.0/22 671 100% 67
2604:1120::/32 No ROA None 635 100% 67
12.17.138.0/23 No ROA Other IRR onlyALTDB 673 100% 67
12.17.176.0/20 No ROA Other IRR onlyALTDB 673 100% 67
12.146.36.0/24 No ROA Other IRR onlyALTDB 673 100% 67
12.146.42.0/24 No ROA Other IRR onlyALTDB 673 100% 67
208.82.56.0/22 No ROA Other IRR onlyALTDB 673 100% 67

AS-SET

AS397602 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 15 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none216.73.140.0/24No ROA covers it. Add a ROA for AS397602, maxLength 24.671 of 673
Route object: none216.73.140.0/24No route object for it. A route object for 216.73.140.0/22 with origin AS397602 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397602 in the RIR database for the space.671 of 673
ROA: none2604:1120::/32No ROA covers it. Add a ROA for AS397602, maxLength 32.635 of 636
Route object: none2604:1120::/32No route object for it. Add a route object with origin AS397602 in the RIR database for the space.635 of 636
ROA: none12.17.138.0/23No ROA covers it. Add a ROA for AS397602, maxLength 23.673 of 673
Route object: RIR12.17.138.0/23Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none12.17.176.0/20No ROA covers it. Add a ROA for AS397602, maxLength 20.673 of 673
Route object: RIR12.17.176.0/20Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none12.146.36.0/24No ROA covers it. Add a ROA for AS397602, maxLength 24.673 of 673
Route object: RIR12.146.36.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none12.146.42.0/24No ROA covers it. Add a ROA for AS397602, maxLength 24.673 of 673
Route object: RIR12.146.42.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none208.82.56.0/22No ROA covers it. Add a ROA for AS397602, maxLength 22.673 of 673
Route object: RIR208.82.56.0/22Route object only in ALTDB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

216.73.140.0/22ALTDBNo 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.