bgpreport

Network · data from 2026-11-12

AS71 Hewlett-Packard AS71

Registry name: HPINC-AMERICAS - HP Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS71, 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.
192.56.8.0/24 No ROA None 673 100% 67
192.56.12.0/24 No ROA None 673 100% 67
192.56.13.0/24 No ROA None 673 100% 67
192.56.15.0/24 No ROA None 673 100% 67
192.56.17.0/24 No ROA None 673 100% 67
192.56.40.0/24 No ROA None 673 100% 67
192.56.45.0/24 No ROA None 673 100% 67
192.56.46.0/24 No ROA None 673 100% 67
192.56.51.0/24 No ROA None 673 100% 67
2620:18d:107::/48 No ROA None 635 100% 67
2620:18d:105::/48 No ROA None 634 100% 67

AS-SET

AS71'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 48 are in fix.csv.

  • ROA: none11
  • Route object: none11
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
ROA: none192.56.8.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.8.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none192.56.12.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.12.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none192.56.13.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.13.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none192.56.15.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.15.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none192.56.17.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.17.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none192.56.40.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.40.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none192.56.45.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.45.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none192.56.46.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.46.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none192.56.51.0/24No ROA covers it. Add a ROA for AS71, maxLength 24.673 of 673
Route object: none192.56.51.0/24No route object for it. Add a route object with origin AS71 in the RIR database for the space.673 of 673
ROA: none2620:18d:107::/48No ROA covers it. Add a ROA for AS71, maxLength 48.635 of 636
Route object: none2620:18d:107::/48No route object for it. Add a route object with origin AS71 in the RIR database for the space.635 of 636
ROA: none2620:18d:105::/48No ROA covers it. Add a ROA for AS71, maxLength 48.634 of 636
Route object: none2620:18d:105::/48No route object for it. Add a route object with origin AS71 in the RIR database for the space.634 of 636

Route objects not announced

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

15.243.176.0/20RADBNo ROA
16.5.4.0/23RADBNo ROA
16.5.8.0/21RADBNo ROA
16.5.12.0/23RADBNo ROA
16.5.14.0/23RADBNo ROA
16.5.16.0/21RADBNo ROA
16.5.24.0/22RADBNo ROA
16.5.40.0/21RADBNo ROA
16.103.140.0/22RADBNo ROA
16.103.152.0/21RADBNo ROA
16.103.160.0/21RADBNo ROA
16.103.164.0/22RADBNo ROA
16.103.180.0/22RADBNo ROA
16.103.184.0/22RADBNo ROA
16.103.208.0/20RADBNo ROA
16.103.212.0/22RADBNo ROA
16.103.216.0/22RADBNo ROA
16.103.220.0/22RADBNo ROA
16.103.224.0/20RADBNo ROA
16.103.228.0/22RADBNo ROA
16.103.232.0/22RADBNo ROA
16.103.236.0/22RADBNo ROA
16.103.240.0/20RADBNo ROA
16.103.241.64/26RADBNo ROA
192.6.70.0/24RIPE-NONAUTHNo ROA
192.170.96.0/19RIPE-NONAUTHNo 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.