bgpreport

Network · data from 2026-11-12

AS400737 AMS-CO-CXO - HEWLETT PACKARD ENTERPRISE COMPANY

Registry name: AMS-CO-CXO - HEWLETT PACKARD ENTERPRISE COMPANY, US · not in PeeringDB

4IPv4 routes 50.0% RPKI valid · 75.0% with a route object
0IPv6 routes
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
0Route objects not announced registered with origin AS400737, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS400737, 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.
16.172.80.0/21 No ROA None 673 100% 67
16.7.40.0/22 No ROA RIR databaseARIN 673 100% 67
16.172.64.0/21 Valid RIR databaseARIN 673 100% 67
16.172.72.0/22 Valid RIR databaseARIN 673 100% 67

AS-SET

AS400737 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 3 are in fix.csv.

  • ROA: none2
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none16.172.80.0/21No ROA covers it. Add a ROA for AS400737, maxLength 21.673 of 673
Route object: none16.172.80.0/21No route object for it. Add a route object with origin AS400737 in the RIR database for the space.673 of 673
ROA: none16.7.40.0/22No ROA covers it. Add a ROA for AS400737, maxLength 22.673 of 673

Route objects not announced

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