bgpreport

Network · data from 2026-11-12

AS400337 ASN-NHB

Registry name: ASN-NHB - NH Broadband, LLC, US · PeeringDB

49IPv4 routes 91.8% RPKI valid · 12.2% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
4RPKI invalid 0 origin · 4 maxLength
0No ROA 43 with no route object for this origin
19Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS400337, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS400337, 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.7.152.0/23 Invalid: maxLength Nonecovered by 38.7.152.0/22 2 0%low visibility 2
38.7.154.0/23 Invalid: maxLength Nonecovered by 38.7.152.0/22 2 0%low visibility 2
38.51.144.0/23 Invalid: maxLength Nonecovered by 38.51.144.0/22 2 0%low visibility 2
38.51.146.0/23 Invalid: maxLength Nonecovered by 38.51.144.0/22 2 0%low visibility 2
38.110.240.0/21 Valid Nonecovered by 38.110.240.0/20 673 100% 67
38.110.240.0/22 Valid Nonecovered by 38.110.240.0/20 673 100% 67
38.110.244.0/22 Valid Nonecovered by 38.110.240.0/20 673 100% 67
38.110.248.0/21 Valid Nonecovered by 38.110.240.0/20 673 100% 67
38.110.248.0/22 Valid Nonecovered by 38.110.240.0/20 673 100% 67
38.110.252.0/22 Valid Nonecovered by 38.110.240.0/20 673 100% 67
134.49.96.0/22 Valid Nonecovered by 134.49.96.0/19 673 100% 67
134.49.100.0/22 Valid Nonecovered by 134.49.96.0/19 673 100% 67
134.49.104.0/22 Valid Nonecovered by 134.49.96.0/19 673 100% 67
134.49.108.0/22 Valid Nonecovered by 134.49.96.0/19 673 100% 67
134.49.112.0/22 Valid Nonecovered by 134.49.96.0/19 673 100% 67
134.49.116.0/22 Valid Nonecovered by 134.49.96.0/19 673 100% 67
134.49.120.0/22 Valid Nonecovered by 134.49.96.0/19 673 100% 67
134.49.124.0/22 Valid Nonecovered by 134.49.96.0/19 673 100% 67
163.245.160.0/20 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.160.0/22 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.164.0/22 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.168.0/22 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.172.0/22 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.176.0/20 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.176.0/22 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.180.0/22 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.184.0/22 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.188.0/22 Valid Nonecovered by 163.245.160.0/19 673 100% 67
163.245.164.0/23 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.166.0/23 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.168.0/23 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.170.0/23 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.172.0/23 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.174.0/23 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.176.0/23 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.178.0/24 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.179.0/24 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.180.0/24 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.181.0/24 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.182.0/24 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.185.0/24 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.187.0/24 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
163.245.188.0/24 Valid Nonecovered by 163.245.160.0/19 2 0%low visibility 2
38.7.152.0/22 Valid RIR databaseARIN, RADB 673 100% 67
38.51.144.0/22 Valid RIR databaseARIN, RADB 673 100% 67
38.110.240.0/20 Valid RIR databaseARIN 673 100% 67
134.49.96.0/19 Valid RIR databaseARIN 673 100% 67
163.245.160.0/19 Valid RIR databaseARIN 673 100% 67
206.225.31.0/24 Valid RIR databaseARIN 673 100% 67
2607:9740::/32 Valid RIR databaseARIN 635 100% 69

AS-SET

AS400337'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 49 are in fix.csv.

  • ROA: maxLength4
  • Route object: none43
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength38.7.152.0/23ROA 38.7.152.0/22 AS400337 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 38.7.152.0/23.2 of 673
Route object: none38.7.152.0/23No route object for it. A route object for 38.7.152.0/22 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
ROA: maxLength38.7.154.0/23ROA 38.7.152.0/22 AS400337 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 38.7.154.0/23.2 of 673
Route object: none38.7.154.0/23No route object for it. A route object for 38.7.152.0/22 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
ROA: maxLength38.51.144.0/23ROA 38.51.144.0/22 AS400337 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 38.51.144.0/23.2 of 673
Route object: none38.51.144.0/23No route object for it. A route object for 38.51.144.0/22 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
ROA: maxLength38.51.146.0/23ROA 38.51.144.0/22 AS400337 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 38.51.146.0/23.2 of 673
Route object: none38.51.146.0/23No route object for it. A route object for 38.51.144.0/22 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none38.110.240.0/21No route object for it. A route object for 38.110.240.0/20 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none38.110.240.0/22No route object for it. A route object for 38.110.240.0/20 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none38.110.244.0/22No route object for it. A route object for 38.110.240.0/20 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none38.110.248.0/21No route object for it. A route object for 38.110.240.0/20 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none38.110.248.0/22No route object for it. A route object for 38.110.240.0/20 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none38.110.252.0/22No route object for it. A route object for 38.110.240.0/20 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none134.49.96.0/22No route object for it. A route object for 134.49.96.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none134.49.100.0/22No route object for it. A route object for 134.49.96.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none134.49.104.0/22No route object for it. A route object for 134.49.96.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none134.49.108.0/22No route object for it. A route object for 134.49.96.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none134.49.112.0/22No route object for it. A route object for 134.49.96.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none134.49.116.0/22No route object for it. A route object for 134.49.96.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none134.49.120.0/22No route object for it. A route object for 134.49.96.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none134.49.124.0/22No route object for it. A route object for 134.49.96.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.160.0/20No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.160.0/22No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.164.0/22No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.168.0/22No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.172.0/22No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.176.0/20No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.176.0/22No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.180.0/22No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.184.0/22No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.188.0/22No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.673 of 673
Route object: none163.245.164.0/23No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.166.0/23No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.168.0/23No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.170.0/23No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.172.0/23No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.174.0/23No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.176.0/23No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.178.0/24No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.179.0/24No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.180.0/24No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.181.0/24No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.182.0/24No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.185.0/24No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.187.0/24No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673
Route object: none163.245.188.0/24No route object for it. A route object for 163.245.160.0/19 with origin AS400337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400337 in the RIR database for the space.2 of 673

Route objects not announced

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

66.231.210.0/24RADBNo ROA
66.231.211.0/24RADBNo 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.