bgpreport

Network · data from 2026-11-12

AS54696 FOOTHILLS-BROADBAND - Foothills Broadband, LLC

Registry name: FOOTHILLS-BROADBAND - Foothills Broadband, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54696, 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.181.164.0/24 Valid Nonecovered by 216.181.164.0/23 672 100% 67
216.181.165.0/24 Valid Nonecovered by 216.181.164.0/23 672 100% 67
23.148.152.0/24 Valid RIR databaseARIN 672 100% 67
23.148.153.0/24 Valid RIR databaseARIN 672 100% 67
23.148.154.0/24 Valid RIR databaseARIN 672 100% 67
23.148.155.0/24 Valid RIR databaseARIN 672 100% 67
69.88.134.0/23 Valid RIR databaseARIN 672 100% 67
167.150.103.0/24 Valid RIR databaseARIN 672 100% 67
204.154.152.0/24 Valid RIR databaseARIN 672 100% 67
208.90.232.0/22 Valid RIR databaseARIN 672 100% 67
208.103.162.0/24 Valid RIR databaseARIN 672 100% 67
216.181.164.0/23 Valid RIR databaseARIN 672 100% 67
2602:fa9e::/36 Valid RIR databaseARIN 635 100% 67

AS-SET

AS54696 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 2 are in fix.csv.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none216.181.164.0/24No route object for it. A route object for 216.181.164.0/23 with origin AS54696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54696 in the RIR database for the space.672 of 673
Route object: none216.181.165.0/24No route object for it. A route object for 216.181.164.0/23 with origin AS54696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54696 in the RIR database for the space.672 of 673

Route objects not announced

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