bgpreport

Network · data from 2026-11-12

AS6071 UNISYS-AS-E - Unisys Corporation

Registry name: UNISYS-AS-E - Unisys Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6071, 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.
129.220.25.0/24 No ROA Nonecovered by 129.220.0.0/18 673 100% 67
129.220.0.0/19 No ROA Nonecovered by 129.220.0.0/18 672 100% 67
129.220.32.0/20 No ROA Nonecovered by 129.220.0.0/18 672 100% 67
129.220.53.0/24 No ROA Nonecovered by 129.220.48.0/20 672 100% 67
129.220.160.0/19 No ROA Nonecovered by 129.220.128.0/17 672 100% 67
129.220.49.0/24 No ROA Nonecovered by 129.220.48.0/20 671 100% 67
129.220.23.0/24 No ROA Other origin onlycovered by 129.220.0.0/18 74 11% 22
129.220.50.0/24 No ROA Other IRR onlyRADB 673 100% 67
129.220.48.0/20 No ROA Other IRR onlyRADB 671 100% 67
129.220.64.0/19 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS6071 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 29 are in fix.csv.

  • ROA: none10
  • Route object: none7
  • Route object: RIR3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none129.220.25.0/24No ROA covers it. Add a ROA for AS6071, maxLength 24.673 of 673
Route object: none129.220.25.0/24No route object for it. A route object for 129.220.0.0/18 with origin AS6071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6071 in the RIR database for the space.673 of 673
ROA: none129.220.0.0/19No ROA covers it. Add a ROA for AS6071, maxLength 19.672 of 673
Route object: none129.220.0.0/19No route object for it. A route object for 129.220.0.0/18 with origin AS6071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6071 in the RIR database for the space.672 of 673
ROA: none129.220.32.0/20No ROA covers it. Add a ROA for AS6071, maxLength 20.672 of 673
Route object: none129.220.32.0/20No route object for it. A route object for 129.220.0.0/18 with origin AS6071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6071 in the RIR database for the space.672 of 673
ROA: none129.220.53.0/24No ROA covers it. Add a ROA for AS6071, maxLength 24.672 of 673
Route object: none129.220.53.0/24No route object for it. A route object for 129.220.48.0/20 with origin AS6071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6071 in the RIR database for the space.672 of 673
ROA: none129.220.160.0/19No ROA covers it. Add a ROA for AS6071, maxLength 19.672 of 673
Route object: none129.220.160.0/19No route object for it. A route object for 129.220.128.0/17 with origin AS6071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6071 in the RIR database for the space.672 of 673
ROA: none129.220.49.0/24No ROA covers it. Add a ROA for AS6071, maxLength 24.671 of 673
Route object: none129.220.49.0/24No route object for it. A route object for 129.220.48.0/20 with origin AS6071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6071 in the RIR database for the space.671 of 673
ROA: none129.220.23.0/24No ROA covers it. Add a ROA for AS6071, maxLength 24.74 of 673
Route object: none129.220.23.0/24Route objects for it name AS2021. A route object for 129.220.0.0/18 with origin AS6071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6071 in the RIR database for the space.74 of 673
ROA: none129.220.50.0/24No ROA covers it. Add a ROA for AS6071, maxLength 24.673 of 673
Route object: RIR129.220.50.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none129.220.48.0/20No ROA covers it. Add a ROA for AS6071, maxLength 20.671 of 673
Route object: RIR129.220.48.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none129.220.64.0/19No ROA covers it. Add a ROA for AS6071, maxLength 19.671 of 673
Route object: RIR129.220.64.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

4.21.144.176/29RADBNo ROA
129.220.0.0/18RADBNo ROA
129.220.128.0/17RADBNo ROA
129.220.192.0/20RADBNo ROA
2620:10c:c000::/40RADBNo ROA
2620:10c:c01c::/48RADBNo ROA
2620:10c:c01d::/48RADBNo ROA
2620:10c:c07f::/48RADBNo ROA
2620:10c:c090::/48RADBNo 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.