bgpreport

Network · data from 2026-11-12

AS20029 H5 Data Centers Denver

Registry name: HCDL-DENVER-DATA-CENTER - H5 Data Centers, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20029, 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.

64.129.78.0/24 No ROA None 673 100% 67
207.188.9.0/24 No ROA Other origin only 673 100% 67
207.188.15.0/24 No ROA Other origin only 673 100% 67
207.188.8.0/24 No ROA Other origin only 671 100% 68
2605:3ac0::/36 No ROA None 635 100% 68
69.67.152.0/24 No ROA Other IRR onlyRADB 671 100% 67
69.67.154.0/24 No ROA RIR databaseARIN 673 100% 67
69.166.104.0/24 No ROA RIR databaseARIN 673 100% 67
69.166.106.0/24 No ROA RIR databaseARIN 673 100% 67
173.205.216.0/24 No ROA RIR databaseARIN 673 100% 67
69.166.107.0/24 No ROA RIR databaseARIN 672 100% 67
173.205.219.0/24 No ROA RIR databaseARIN 672 100% 67
207.188.13.0/24 No ROA RIR databaseARIN 672 100% 67
207.188.14.0/24 No ROA RIR databaseARIN 672 100% 67

AS-SET

AS20029'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 20 are in fix.csv.

  • ROA: none14
  • Route object: none5
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none64.129.78.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.673 of 673
Route object: none64.129.78.0/24No route object for it. Add a route object with origin AS20029 in the RIR database for the space.673 of 673
ROA: none207.188.9.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.673 of 673
Route object: none207.188.9.0/24Route objects for it name AS400824. Add a route object with origin AS20029 in the RIR database for the space.673 of 673
ROA: none207.188.15.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.673 of 673
Route object: none207.188.15.0/24Route objects for it name AS400821. Add a route object with origin AS20029 in the RIR database for the space.673 of 673
ROA: none207.188.8.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.671 of 673
Route object: none207.188.8.0/24Route objects for it name AS400825. Add a route object with origin AS20029 in the RIR database for the space.671 of 673
ROA: none2605:3ac0::/36No ROA covers it. Add a ROA for AS20029, maxLength 36.635 of 636
Route object: none2605:3ac0::/36No route object for it. Add a route object with origin AS20029 in the RIR database for the space.635 of 636
ROA: none69.67.152.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.671 of 673
Route object: RIR69.67.152.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.67.154.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.673 of 673
ROA: none69.166.104.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.673 of 673
ROA: none69.166.106.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.673 of 673
ROA: none173.205.216.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.673 of 673
ROA: none69.166.107.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.672 of 673
ROA: none173.205.219.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.672 of 673
ROA: none207.188.13.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.672 of 673
ROA: none207.188.14.0/24No ROA covers it. Add a ROA for AS20029, maxLength 24.672 of 673

Route objects not announced

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