bgpreport

Network · data from 2026-11-12

AS139139 SYAUNET - Shenyang Agricultural University

Registry name: SYAUNET - Shenyang Agricultural University, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139139, 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.
103.152.186.0/24 Valid Nonecovered by 103.152.186.0/23 673 100% 67
103.152.187.0/24 Valid Nonecovered by 103.152.186.0/23 673 100% 67
2406:3340::/36 Valid Nonecovered by 2406:3340::/32 61 10%low visibility 37
2406:3340:1000::/36 Valid Nonecovered by 2406:3340::/32 61 10%low visibility 37
2406:3340:2000::/36 Valid Nonecovered by 2406:3340::/32 20 3%low visibility 13
2406:3340:3000::/36 Valid Nonecovered by 2406:3340::/32 20 3%low visibility 13
103.152.186.0/23 Valid RIR databaseALTDB, APNIC, NTTCOM 673 100% 67
2406:3340::/32 Valid RIR databaseALTDB, APNIC, NTTCOM 635 100% 70

AS-SET

AS139139 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 6 are in fix.csv.

  • Route object: none6
ChangePrefix or setDetailFull-table peers
Route object: none103.152.186.0/24No route object for it. A route object for 103.152.186.0/23 with origin AS139139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139139 in the RIR database for the space.673 of 673
Route object: none103.152.187.0/24No route object for it. A route object for 103.152.186.0/23 with origin AS139139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139139 in the RIR database for the space.673 of 673
Route object: none2406:3340::/36No route object for it. A route object for 2406:3340::/32 with origin AS139139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139139 in the RIR database for the space.61 of 636
Route object: none2406:3340:1000::/36No route object for it. A route object for 2406:3340::/32 with origin AS139139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139139 in the RIR database for the space.61 of 636
Route object: none2406:3340:2000::/36No route object for it. A route object for 2406:3340::/32 with origin AS139139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139139 in the RIR database for the space.20 of 636
Route object: none2406:3340:3000::/36No route object for it. A route object for 2406:3340::/32 with origin AS139139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139139 in the RIR database for the space.20 of 636

Route objects not announced

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