bgpreport

Network · data from 2026-11-12

AS401548 H5 Data Centers Omaha

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401548, 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.
2605:3ac0:5000::/40 No ROA Nonecovered by 2605:3ac0:5000::/36 633 100% 67
130.250.164.0/24 No ROA RIR databaseARIN 672 100% 67

AS-SET

AS401548'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: none2
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2605:3ac0:5000::/40No ROA covers it. Add a ROA for AS401548, maxLength 40.633 of 636
Route object: none2605:3ac0:5000::/40No route object for it. A route object for 2605:3ac0:5000::/36 with origin AS401548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401548 in the RIR database for the space.633 of 636
ROA: none130.250.164.0/24No ROA covers it. Add a ROA for AS401548, maxLength 24.672 of 673

Route objects not announced

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

2605:3ac0:5000::/36ARINNo 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.