bgpreport

Network · data from 2026-11-12

AS25582 ASN-LINIX NWIP Ltd

Registry name: ASN-LINIX NWIP Ltd, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25582, 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.

217.14.177.0/24 No ROA Nonecovered by 217.14.176.0/21 672 100% 66
217.14.178.0/23 No ROA Nonecovered by 217.14.176.0/21 672 100% 66
217.28.16.0/23 No ROA Nonecovered by 217.28.16.0/21 672 100% 66
217.28.18.0/24 No ROA Nonecovered by 217.28.16.0/21 672 100% 66
217.28.19.0/24 No ROA Nonecovered by 217.28.16.0/21 672 100% 66
217.28.21.0/24 No ROA Nonecovered by 217.28.16.0/21 672 100% 66
217.14.176.0/21 No ROA RIR databaseRIPE 673 100% 66
217.28.16.0/21 No ROA RIR databaseRIPE 673 100% 66
2a09:1740::/29 No ROA RIR databaseRIPE 635 100% 67

AS-SET

AS25582 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 15 are in fix.csv.

  • ROA: none9
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none217.14.177.0/24No ROA covers it. Add a ROA for AS25582, maxLength 24.672 of 673
Route object: none217.14.177.0/24No route object for it. A route object for 217.14.176.0/21 with origin AS25582 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25582 in the RIR database for the space.672 of 673
ROA: none217.14.178.0/23No ROA covers it. Add a ROA for AS25582, maxLength 23.672 of 673
Route object: none217.14.178.0/23No route object for it. A route object for 217.14.176.0/21 with origin AS25582 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25582 in the RIR database for the space.672 of 673
ROA: none217.28.16.0/23No ROA covers it. Add a ROA for AS25582, maxLength 23.672 of 673
Route object: none217.28.16.0/23No route object for it. A route object for 217.28.16.0/21 with origin AS25582 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25582 in the RIR database for the space.672 of 673
ROA: none217.28.18.0/24No ROA covers it. Add a ROA for AS25582, maxLength 24.672 of 673
Route object: none217.28.18.0/24No route object for it. A route object for 217.28.16.0/21 with origin AS25582 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25582 in the RIR database for the space.672 of 673
ROA: none217.28.19.0/24No ROA covers it. Add a ROA for AS25582, maxLength 24.672 of 673
Route object: none217.28.19.0/24No route object for it. A route object for 217.28.16.0/21 with origin AS25582 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25582 in the RIR database for the space.672 of 673
ROA: none217.28.21.0/24No ROA covers it. Add a ROA for AS25582, maxLength 24.672 of 673
Route object: none217.28.21.0/24No route object for it. A route object for 217.28.16.0/21 with origin AS25582 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25582 in the RIR database for the space.672 of 673
ROA: none217.14.176.0/21No ROA covers it. Add a ROA for AS25582, maxLength 21.673 of 673
ROA: none217.28.16.0/21No ROA covers it. Add a ROA for AS25582, maxLength 21.673 of 673
ROA: none2a09:1740::/29No ROA covers it. Add a ROA for AS25582, maxLength 29.635 of 636

Route objects not announced

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