Network · data from 2026-11-12
AS17711 NDHU-TW - National Dong Hwa University
Registry name: NDHU-TW - National Dong Hwa University, TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17711, 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.36.0/22 | Invalid: origin | None | 1 0%low visibility |
| 210.59.6.0/23 | Invalid: origin | None | 1 0%low visibility |
| 210.240.96.0/21 | Invalid: origin | None | 1 0%low visibility |
| 210.240.104.0/24 | Invalid: origin | None | 1 0%low visibility |
| 134.208.0.0/17 | Invalid: maxLength | None | 1 0%low visibility |
| 134.208.128.0/17 | Invalid: maxLength | None | 1 0%low visibility |
| 163.28.160.0/20 | Valid | None | 1 0%low visibility |
| 203.64.34.0/23 | Valid | None | 1 0%low visibility |
| 203.64.40.0/22 | Valid | None | 1 0%low visibility |
| 203.64.76.0/22 | Valid | None | 1 0%low visibility |
| 203.64.80.0/21 | Valid | None | 1 0%low visibility |
| 203.68.24.0/23 | Valid | None | 1 0%low visibility |
| 203.68.59.0/24 | Valid | None | 1 0%low visibility |
| 203.68.60.0/22 | Valid | None | 1 0%low visibility |
| 203.68.72.0/24 | Valid | None | 1 0%low visibility |
| 203.68.153.0/24 | Valid | None | 1 0%low visibility |
| 203.68.154.0/23 | Valid | None | 1 0%low visibility |
| 203.68.200.0/23 | Valid | None | 1 0%low visibility |
| 203.68.210.0/24 | Valid | None | 1 0%low visibility |
| 203.71.0.0/23 | Valid | None | 1 0%low visibility |
| 203.71.58.0/23 | Valid | None | 1 0%low visibility |
| 203.71.60.0/23 | Valid | None | 1 0%low visibility |
| 203.71.244.0/24 | Valid | None | 1 0%low visibility |
| 203.72.48.0/22 | Valid | None | 1 0%low visibility |
| 203.72.73.0/24 | Valid | None | 1 0%low visibility |
| 203.72.74.0/23 | Valid | None | 1 0%low visibility |
| 203.72.76.0/22 | Valid | None | 1 0%low visibility |
| 203.72.80.0/21 | Valid | None | 1 0%low visibility |
| 203.72.94.0/24 | Valid | None | 1 0%low visibility |
| 210.62.247.0/24 | Valid | None | 1 0%low visibility |
| 210.243.52.0/23 | Valid | None | 1 0%low visibility |
| 210.243.54.0/24 | Valid | None | 1 0%low visibility |
AS-SET
AS17711 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 38 are in fix.csv.
- ROA: origin4
- ROA: maxLength2
- Route object: none32
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 203.64.36.0/22 | ROAs covering it name AS1659, not AS17711. If AS17711 should announce it, add a ROA for AS17711. |
| Route object: none | 203.64.36.0/22 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| ROA: origin | 210.59.6.0/23 | ROAs covering it name AS1659, not AS17711. If AS17711 should announce it, add a ROA for AS17711. |
| Route object: none | 210.59.6.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| ROA: origin | 210.240.96.0/21 | ROAs covering it name AS1659, not AS17711. If AS17711 should announce it, add a ROA for AS17711. |
| Route object: none | 210.240.96.0/21 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| ROA: origin | 210.240.104.0/24 | ROAs covering it name AS1659, not AS17711. If AS17711 should announce it, add a ROA for AS17711. |
| Route object: none | 210.240.104.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| ROA: maxLength | 134.208.0.0/17 | ROA 134.208.0.0/16 AS17711 has maxLength 16; the route is a /17. Raise the maxLength, or add a ROA for 134.208.0.0/17. |
| Route object: none | 134.208.0.0/17 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| ROA: maxLength | 134.208.128.0/17 | ROA 134.208.0.0/16 AS17711 has maxLength 16; the route is a /17. Raise the maxLength, or add a ROA for 134.208.128.0/17. |
| Route object: none | 134.208.128.0/17 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 163.28.160.0/20 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.64.34.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.64.40.0/22 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.64.76.0/22 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.64.80.0/21 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.68.24.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.68.59.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.68.60.0/22 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.68.72.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.68.153.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.68.154.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.68.200.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.68.210.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.71.0.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.71.58.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.71.60.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.71.244.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.72.48.0/22 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.72.73.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.72.74.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.72.76.0/22 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.72.80.0/21 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 203.72.94.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 210.62.247.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 210.243.52.0/23 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
| Route object: none | 210.243.54.0/24 | No route object for it. Add a route object with origin AS17711 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS17711 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.