Network · data from 2026-11-12
AS9916 National Yang Ming Chiao Tung University
Registry name: NCTU-TW - National Yang Ming Chiao Tung University, TW · PeeringDB
45IPv4 routes
93.3% RPKI valid · 24.4% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
3RPKI invalid
3 origin · 0 maxLength
0No ROA
34 with no route object for this origin
36Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS9916, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS9916, 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.64.246.0/23 | Invalid: origin | None | 1 0%low visibility |
| 203.64.248.0/22 | Invalid: origin | None | 1 0%low visibility |
| 203.68.219.0/24 | Invalid: origin | None | 1 0%low visibility |
| 192.83.180.0/24 | Valid | None | 8 1%low visibility |
| 120.104.0.0/16 | Valid | None | 1 0%low visibility |
| 120.105.0.0/16 | Valid | None | 1 0%low visibility |
| 120.106.0.0/18 | Valid | None | 1 0%low visibility |
| 120.106.64.0/21 | Valid | None | 1 0%low visibility |
| 120.106.72.0/21 | Valid | None | 1 0%low visibility |
| 120.106.80.0/20 | Valid | None | 1 0%low visibility |
| 120.106.96.0/20 | Valid | None | 1 0%low visibility |
| 120.106.112.0/21 | Valid | None | 1 0%low visibility |
| 120.106.120.0/24 | Valid | None | 1 0%low visibility |
| 120.106.121.0/24 | Valid | None | 1 0%low visibility |
| 120.106.122.0/24 | Valid | None | 1 0%low visibility |
| 120.106.123.0/24 | Valid | None | 1 0%low visibility |
| 120.106.124.0/24 | Valid | None | 1 0%low visibility |
| 120.106.125.0/24 | Valid | None | 1 0%low visibility |
| 120.106.126.0/24 | Valid | None | 1 0%low visibility |
| 120.106.128.0/18 | Valid | None | 1 0%low visibility |
| 120.106.192.0/18 | Valid | None | 1 0%low visibility |
| 163.28.64.0/24 | Valid | None | 1 0%low visibility |
| 192.83.179.0/24 | Valid | None | 1 0%low visibility |
| 203.64.172.0/22 | Valid | None | 1 0%low visibility |
| 203.64.176.0/21 | Valid | None | 1 0%low visibility |
| 203.64.184.0/22 | Valid | None | 1 0%low visibility |
| 203.68.172.0/22 | Valid | None | 1 0%low visibility |
| 203.71.213.0/24 | Valid | None | 1 0%low visibility |
| 203.72.71.0/24 | Valid | None | 1 0%low visibility |
| 203.72.72.0/24 | Valid | None | 1 0%low visibility |
| 210.60.55.0/24 | Valid | None | 1 0%low visibility |
| 210.60.166.0/23 | Valid | None | 1 0%low visibility |
| 210.60.168.0/22 | Valid | None | 1 0%low visibility |
| 210.240.200.0/23 | Valid | None | 1 0%low visibility |
| 120.126.32.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 120.126.64.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 120.126.96.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 140.113.0.0/16 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 140.129.51.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 140.129.52.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 140.129.56.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 140.129.64.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 140.129.80.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2001:f18::/32 | Valid | Other IRR onlyNTTCOM, RADB | 636 100% |
| 140.126.0.0/16 | Valid | Other IRR onlyNTTCOM | 1 0%low visibility |
| 163.19.0.0/16 | Valid | Other IRR onlyNTTCOM | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS9916: AS-NCTU. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS9916 isn't in the set, or no route object for AS9916 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS9916 in it | Not covered |
|---|---|---|---|---|---|
| AS-NCTU | APNIC | 5 | 1 | Yes | 34 |
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 49 are in fix.csv.
- ROA: origin3
- Route object: none34
- Route object: RIR12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 203.64.246.0/23 | ROAs covering it name AS1659, not AS9916. If AS9916 should announce it, add a ROA for AS9916. |
| Route object: none | 203.64.246.0/23 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| ROA: origin | 203.64.248.0/22 | ROAs covering it name AS1659, not AS9916. If AS9916 should announce it, add a ROA for AS9916. |
| Route object: none | 203.64.248.0/22 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| ROA: origin | 203.68.219.0/24 | ROAs covering it name AS1659, not AS9916. If AS9916 should announce it, add a ROA for AS9916. |
| Route object: none | 203.68.219.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 192.83.180.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.104.0.0/16 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.105.0.0/16 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.0.0/18 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.64.0/21 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.72.0/21 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.80.0/20 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.96.0/20 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.112.0/21 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.120.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.121.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.122.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.123.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.124.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.125.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.126.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.128.0/18 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 120.106.192.0/18 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 163.28.64.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 192.83.179.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 203.64.172.0/22 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 203.64.176.0/21 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 203.64.184.0/22 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 203.68.172.0/22 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 203.71.213.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 203.72.71.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 203.72.72.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 210.60.55.0/24 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 210.60.166.0/23 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 210.60.168.0/22 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: none | 210.240.200.0/23 | No route object for it. Add a route object with origin AS9916 in the RIR database for the space. |
| Route object: RIR | 120.126.32.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 120.126.64.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 120.126.96.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 140.113.0.0/16 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 140.129.51.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 140.129.52.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 140.129.56.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 140.129.64.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 140.129.80.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:f18::/32 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 140.126.0.0/16 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 163.19.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 AS9916 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.