Network · data from 2026-11-12
AS17713 NSYSU-TW - Ministry of Education Computer Center
Registry name: NSYSU-TW - Ministry of Education Computer Center, TW · not in PeeringDB
39IPv4 routes
97.4% RPKI valid · 2.6% with a route object
0IPv6 routes
1RPKI invalid
1 origin · 0 maxLength
0No ROA
38 with no route object for this origin
39Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS17713, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS17713, 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.
| 203.71.208.0/23 | Invalid: origin | None | 1 0%low visibility |
| 140.133.32.0/19 | Valid | None | 1 0%low visibility |
| 140.133.64.0/20 | Valid | None | 1 0%low visibility |
| 140.133.80.0/21 | Valid | None | 1 0%low visibility |
| 140.133.88.0/22 | Valid | None | 1 0%low visibility |
| 140.133.92.0/23 | Valid | None | 1 0%low visibility |
| 192.83.191.0/24 | Valid | None | 1 0%low visibility |
| 192.83.194.0/23 | Valid | None | 1 0%low visibility |
| 192.192.178.0/24 | Valid | None | 1 0%low visibility |
| 192.192.190.0/23 | Valid | None | 1 0%low visibility |
| 192.192.192.0/22 | Valid | None | 1 0%low visibility |
| 192.192.214.0/23 | Valid | None | 1 0%low visibility |
| 192.192.216.0/22 | Valid | None | 1 0%low visibility |
| 203.64.54.0/23 | Valid | None | 1 0%low visibility |
| 203.64.56.0/21 | Valid | None | 1 0%low visibility |
| 203.64.64.0/23 | Valid | None | 1 0%low visibility |
| 203.64.88.0/21 | Valid | None | 1 0%low visibility |
| 203.64.96.0/21 | Valid | None | 1 0%low visibility |
| 203.64.120.0/21 | Valid | None | 1 0%low visibility |
| 203.64.128.0/21 | Valid | None | 1 0%low visibility |
| 203.64.166.0/23 | Valid | None | 1 0%low visibility |
| 203.64.168.0/22 | Valid | None | 1 0%low visibility |
| 203.68.0.0/22 | Valid | None | 1 0%low visibility |
| 203.68.4.0/23 | Valid | None | 1 0%low visibility |
| 203.68.94.0/23 | Valid | None | 1 0%low visibility |
| 203.68.96.0/22 | Valid | None | 1 0%low visibility |
| 203.71.232.0/23 | Valid | None | 1 0%low visibility |
| 203.72.211.0/24 | Valid | None | 1 0%low visibility |
| 210.60.80.0/21 | Valid | None | 1 0%low visibility |
| 210.60.88.0/22 | Valid | None | 1 0%low visibility |
| 210.60.92.0/24 | Valid | None | 1 0%low visibility |
| 210.60.147.0/24 | Valid | None | 1 0%low visibility |
| 210.60.148.0/24 | Valid | None | 1 0%low visibility |
| 210.60.183.0/24 | Valid | None | 1 0%low visibility |
| 210.60.184.0/22 | Valid | None | 1 0%low visibility |
| 210.60.188.0/23 | Valid | None | 1 0%low visibility |
| 210.60.190.0/24 | Valid | None | 1 0%low visibility |
| 210.70.254.0/24 | Valid | None | 1 0%low visibility |
| 140.117.0.0/16 | Valid | Other IRR onlyNTTCOM | 17 3%low visibility |
AS-SET
AS17713 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 40 are in fix.csv.
- ROA: origin1
- Route object: none38
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 203.71.208.0/23 | ROAs covering it name AS1659, not AS17713. If AS17713 should announce it, add a ROA for AS17713. |
| Route object: none | 203.71.208.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 140.133.32.0/19 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 140.133.64.0/20 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 140.133.80.0/21 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 140.133.88.0/22 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 140.133.92.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 192.83.191.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 192.83.194.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 192.192.178.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 192.192.190.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 192.192.192.0/22 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 192.192.214.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 192.192.216.0/22 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.54.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.56.0/21 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.64.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.88.0/21 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.96.0/21 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.120.0/21 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.128.0/21 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.166.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.64.168.0/22 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.68.0.0/22 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.68.4.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.68.94.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.68.96.0/22 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.71.232.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 203.72.211.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.80.0/21 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.88.0/22 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.92.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.147.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.148.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.183.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.184.0/22 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.188.0/23 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.60.190.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: none | 210.70.254.0/24 | No route object for it. Add a route object with origin AS17713 in the RIR database for the space. |
| Route object: RIR | 140.117.0.0/16 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS17713 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.