bgpreport

Network · data from 2026-11-12

AS13342

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

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

12.195.180.0/23 Invalid: origin Other origin only 2 0%low visibility 2
68.156.127.0/24 Invalid: origin Other origin only 2 0%low visibility 2
70.151.33.0/24 Invalid: origin Other origin only 2 0%low visibility 2
70.159.12.0/23 Invalid: origin Other origin only 2 0%low visibility 2
72.159.38.0/23 Invalid: origin Other origin only 2 0%low visibility 2
74.174.130.0/24 Invalid: origin Other origin only 2 0%low visibility 2
74.174.131.0/24 Invalid: origin Other origin only 2 0%low visibility 2
74.254.196.0/23 Invalid: origin Other origin only 2 0%low visibility 2
74.254.204.0/23 Invalid: origin Other origin only 2 0%low visibility 2
74.254.206.0/23 Invalid: origin Other origin only 2 0%low visibility 2
208.61.241.0/24 Invalid: origin Other origin only 2 0%low visibility 2
216.77.68.0/24 Invalid: origin Other origin only 1 0%low visibility 1
209.215.71.0/24 No ROA None 2 0%low visibility 2
209.215.186.0/23 No ROA None 1 0%low visibility 1

AS-SET

AS13342 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 28 are in fix.csv.

  • ROA: origin12
  • ROA: none2
  • Route object: none14
ChangePrefix or setDetailFull-table peers
ROA: origin12.195.180.0/23ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none12.195.180.0/23Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin68.156.127.0/24ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none68.156.127.0/24Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin70.151.33.0/24ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none70.151.33.0/24Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin70.159.12.0/23ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none70.159.12.0/23Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin72.159.38.0/23ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none72.159.38.0/23Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin74.174.130.0/24ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none74.174.130.0/24Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin74.174.131.0/24ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none74.174.131.0/24Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin74.254.196.0/23ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none74.254.196.0/23Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin74.254.204.0/23ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none74.254.204.0/23Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin74.254.206.0/23ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none74.254.206.0/23Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin208.61.241.0/24ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.2 of 673
Route object: none208.61.241.0/24Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: origin216.77.68.0/24ROAs covering it name AS2386, not AS13342. If AS13342 should announce it, add a ROA for AS13342.1 of 673
Route object: none216.77.68.0/24Route objects for it name AS2386. Add a route object with origin AS13342 in the RIR database for the space.1 of 673
ROA: none209.215.71.0/24No ROA covers it. Add a ROA for AS13342, maxLength 24.2 of 673
Route object: none209.215.71.0/24No route object for it. Add a route object with origin AS13342 in the RIR database for the space.2 of 673
ROA: none209.215.186.0/23No ROA covers it. Add a ROA for AS13342, maxLength 23.1 of 673
Route object: none209.215.186.0/23No route object for it. Add a route object with origin AS13342 in the RIR database for the space.1 of 673

Route objects not announced

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