bgpreport

Network · data from 2026-11-12

AS14417 LANDSTAR - Landstar System Inc

Registry name: LANDSTAR - Landstar System Inc, US · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 25.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No 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 AS14417, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS14417, 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.
170.203.248.0/24 No ROA None 673 100% 67
170.203.249.0/24 No ROA Other origin only 673 100% 67
170.203.252.0/24 No ROA None 673 100% 67
170.203.253.0/24 No ROA None 673 100% 67
170.203.254.0/24 No ROA None 673 100% 67
170.203.255.0/24 No ROA None 673 100% 67
170.203.250.0/24 No ROA Other IRR onlyRADB 673 100% 67
170.203.251.0/24 No ROA Other IRR onlyRADB 668 99% 66

AS-SET

AS14417 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none170.203.248.0/24No ROA covers it. Add a ROA for AS14417, maxLength 24.673 of 673
Route object: none170.203.248.0/24No route object for it. Add a route object with origin AS14417 in the RIR database for the space.673 of 673
ROA: none170.203.249.0/24No ROA covers it. Add a ROA for AS14417, maxLength 24.673 of 673
Route object: none170.203.249.0/24Route objects for it name AS36351. Add a route object with origin AS14417 in the RIR database for the space.673 of 673
ROA: none170.203.252.0/24No ROA covers it. Add a ROA for AS14417, maxLength 24.673 of 673
Route object: none170.203.252.0/24No route object for it. Add a route object with origin AS14417 in the RIR database for the space.673 of 673
ROA: none170.203.253.0/24No ROA covers it. Add a ROA for AS14417, maxLength 24.673 of 673
Route object: none170.203.253.0/24No route object for it. Add a route object with origin AS14417 in the RIR database for the space.673 of 673
ROA: none170.203.254.0/24No ROA covers it. Add a ROA for AS14417, maxLength 24.673 of 673
Route object: none170.203.254.0/24No route object for it. Add a route object with origin AS14417 in the RIR database for the space.673 of 673
ROA: none170.203.255.0/24No ROA covers it. Add a ROA for AS14417, maxLength 24.673 of 673
Route object: none170.203.255.0/24No route object for it. Add a route object with origin AS14417 in the RIR database for the space.673 of 673
ROA: none170.203.250.0/24No ROA covers it. Add a ROA for AS14417, maxLength 24.673 of 673
Route object: RIR170.203.250.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.203.251.0/24No ROA covers it. Add a ROA for AS14417, maxLength 24.668 of 673
Route object: RIR170.203.251.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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