bgpreport

Network · data from 2026-11-12

AS399610 AMS-HST - HEWLETT PACKARD ENTERPRISE COMPANY

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399610, 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.9.0.0/17 No ROA None 673 100% 67
16.103.0.0/24 No ROA None 673 100% 67
16.103.1.0/24 No ROA None 673 100% 67
16.103.2.0/24 No ROA None 673 100% 67
16.103.3.0/24 No ROA None 673 100% 67
16.103.8.0/21 No ROA None 673 100% 67
16.103.16.0/21 No ROA None 673 100% 67
16.103.24.0/23 No ROA None 673 100% 67
16.103.32.0/20 No ROA None 673 100% 67

AS-SET

AS399610 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 18 are in fix.csv.

  • ROA: none9
  • Route object: none9
ChangePrefix or setDetailFull-table peers
ROA: none16.9.0.0/17No ROA covers it. Add a ROA for AS399610, maxLength 17.673 of 673
Route object: none16.9.0.0/17No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673
ROA: none16.103.0.0/24No ROA covers it. Add a ROA for AS399610, maxLength 24.673 of 673
Route object: none16.103.0.0/24No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673
ROA: none16.103.1.0/24No ROA covers it. Add a ROA for AS399610, maxLength 24.673 of 673
Route object: none16.103.1.0/24No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673
ROA: none16.103.2.0/24No ROA covers it. Add a ROA for AS399610, maxLength 24.673 of 673
Route object: none16.103.2.0/24No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673
ROA: none16.103.3.0/24No ROA covers it. Add a ROA for AS399610, maxLength 24.673 of 673
Route object: none16.103.3.0/24No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673
ROA: none16.103.8.0/21No ROA covers it. Add a ROA for AS399610, maxLength 21.673 of 673
Route object: none16.103.8.0/21No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673
ROA: none16.103.16.0/21No ROA covers it. Add a ROA for AS399610, maxLength 21.673 of 673
Route object: none16.103.16.0/21No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673
ROA: none16.103.24.0/23No ROA covers it. Add a ROA for AS399610, maxLength 23.673 of 673
Route object: none16.103.24.0/23No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673
ROA: none16.103.32.0/20No ROA covers it. Add a ROA for AS399610, maxLength 20.673 of 673
Route object: none16.103.32.0/20No route object for it. Add a route object with origin AS399610 in the RIR database for the space.673 of 673

Route objects not announced

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