bgpreport

Network · data from 2026-11-12

AS17052 TARGET - Target Corporation

Registry name: TARGET - Target Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17052, 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.
161.225.0.0/16 No ROA None 673 100% 67
161.225.80.0/20 No ROA None 673 100% 67
161.225.254.0/24 No ROA None 673 100% 67
170.195.0.0/17 No ROA None 673 100% 67
170.195.0.0/18 No ROA None 673 100% 67
170.195.64.0/18 No ROA None 673 100% 67
161.225.64.0/20 No ROA None 672 100% 67
161.225.255.0/24 No ROA None 671 100% 67

AS-SET

AS17052 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: none8
ChangePrefix or setDetailFull-table peers
ROA: none161.225.0.0/16No ROA covers it. Add a ROA for AS17052, maxLength 16.673 of 673
Route object: none161.225.0.0/16No route object for it. Add a route object with origin AS17052 in the RIR database for the space.673 of 673
ROA: none161.225.80.0/20No ROA covers it. Add a ROA for AS17052, maxLength 20.673 of 673
Route object: none161.225.80.0/20No route object for it. Add a route object with origin AS17052 in the RIR database for the space.673 of 673
ROA: none161.225.254.0/24No ROA covers it. Add a ROA for AS17052, maxLength 24.673 of 673
Route object: none161.225.254.0/24No route object for it. Add a route object with origin AS17052 in the RIR database for the space.673 of 673
ROA: none170.195.0.0/17No ROA covers it. Add a ROA for AS17052, maxLength 17.673 of 673
Route object: none170.195.0.0/17No route object for it. Add a route object with origin AS17052 in the RIR database for the space.673 of 673
ROA: none170.195.0.0/18No ROA covers it. Add a ROA for AS17052, maxLength 18.673 of 673
Route object: none170.195.0.0/18No route object for it. Add a route object with origin AS17052 in the RIR database for the space.673 of 673
ROA: none170.195.64.0/18No ROA covers it. Add a ROA for AS17052, maxLength 18.673 of 673
Route object: none170.195.64.0/18No route object for it. Add a route object with origin AS17052 in the RIR database for the space.673 of 673
ROA: none161.225.64.0/20No ROA covers it. Add a ROA for AS17052, maxLength 20.672 of 673
Route object: none161.225.64.0/20No route object for it. Add a route object with origin AS17052 in the RIR database for the space.672 of 673
ROA: none161.225.255.0/24No ROA covers it. Add a ROA for AS17052, maxLength 24.671 of 673
Route object: none161.225.255.0/24No route object for it. Add a route object with origin AS17052 in the RIR database for the space.671 of 673

Route objects not announced

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