bgpreport

Network · data from 2026-11-12

AS400828 H5 Data Centers Atlanta

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400828, 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.
65.100.156.0/24 No ROA None 673 100% 67
173.205.217.0/24 No ROA RIR databaseARIN 673 100% 67
2605:3ac0:c000::/36 No ROA RIR databaseARIN 635 100% 68

AS-SET

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

  • ROA: none3
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none65.100.156.0/24No ROA covers it. Add a ROA for AS400828, maxLength 24.673 of 673
Route object: none65.100.156.0/24No route object for it. Add a route object with origin AS400828 in the RIR database for the space.673 of 673
ROA: none173.205.217.0/24No ROA covers it. Add a ROA for AS400828, maxLength 24.673 of 673
ROA: none2605:3ac0:c000::/36No ROA covers it. Add a ROA for AS400828, maxLength 36.635 of 636

Route objects not announced

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