bgpreport

Network · data from 2026-11-12

AS151229 SAUNET - Shenyang Aerospace University

Registry name: SAUNET - Shenyang Aerospace University, CN · not in PeeringDB

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

Announced routes

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

2402:18a0::/33 Invalid: maxLength None 5 1%low visibility 4
58.154.16.0/20 No ROA Other origin only 57 8%low visibility 32
59.73.128.0/19 No ROA Other origin only 57 8%low visibility 32
59.73.160.0/21 No ROA Other origin only 57 8%low visibility 32
202.199.24.0/21 No ROA Other origin only 57 8%low visibility 32
2402:18a0::/32 Valid None 3 0%low visibility 3
165.101.208.0/23 Valid Other IRR onlyRADB 671 100% 68

AS-SET

AS151229 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 12 are in fix.csv.

  • ROA: maxLength1
  • ROA: none4
  • Route object: none6
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2402:18a0::/33ROA 2402:18a0::/32 AS151229 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2402:18a0::/33.5 of 636
Route object: none2402:18a0::/33No route object for it. Add a route object with origin AS151229 in the RIR database for the space.5 of 636
ROA: none58.154.16.0/20No ROA covers it. Add a ROA for AS151229, maxLength 20.57 of 673
Route object: none58.154.16.0/20Route objects for it name AS4538. Add a route object with origin AS151229 in the RIR database for the space.57 of 673
ROA: none59.73.128.0/19No ROA covers it. Add a ROA for AS151229, maxLength 19.57 of 673
Route object: none59.73.128.0/19Route objects for it name AS4538. Add a route object with origin AS151229 in the RIR database for the space.57 of 673
ROA: none59.73.160.0/21No ROA covers it. Add a ROA for AS151229, maxLength 21.57 of 673
Route object: none59.73.160.0/21Route objects for it name AS4538. Add a route object with origin AS151229 in the RIR database for the space.57 of 673
ROA: none202.199.24.0/21No ROA covers it. Add a ROA for AS151229, maxLength 21.57 of 673
Route object: none202.199.24.0/21Route objects for it name AS4538. Add a route object with origin AS151229 in the RIR database for the space.57 of 673
Route object: none2402:18a0::/32No route object for it. Add a route object with origin AS151229 in the RIR database for the space.3 of 636
Route object: RIR165.101.208.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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