bgpreport

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

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

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 1
210.59.6.0/23 Invalid: origin None 1 0%low visibility 1
210.240.96.0/21 Invalid: origin None 1 0%low visibility 1
210.240.104.0/24 Invalid: origin None 1 0%low visibility 1
134.208.0.0/17 Invalid: maxLength None 1 0%low visibility 1
134.208.128.0/17 Invalid: maxLength None 1 0%low visibility 1
163.28.160.0/20 Valid None 1 0%low visibility 1
203.64.34.0/23 Valid None 1 0%low visibility 1
203.64.40.0/22 Valid None 1 0%low visibility 1
203.64.76.0/22 Valid None 1 0%low visibility 1
203.64.80.0/21 Valid None 1 0%low visibility 1
203.68.24.0/23 Valid None 1 0%low visibility 1
203.68.59.0/24 Valid None 1 0%low visibility 1
203.68.60.0/22 Valid None 1 0%low visibility 1
203.68.72.0/24 Valid None 1 0%low visibility 1
203.68.153.0/24 Valid None 1 0%low visibility 1
203.68.154.0/23 Valid None 1 0%low visibility 1
203.68.200.0/23 Valid None 1 0%low visibility 1
203.68.210.0/24 Valid None 1 0%low visibility 1
203.71.0.0/23 Valid None 1 0%low visibility 1
203.71.58.0/23 Valid None 1 0%low visibility 1
203.71.60.0/23 Valid None 1 0%low visibility 1
203.71.244.0/24 Valid None 1 0%low visibility 1
203.72.48.0/22 Valid None 1 0%low visibility 1
203.72.73.0/24 Valid None 1 0%low visibility 1
203.72.74.0/23 Valid None 1 0%low visibility 1
203.72.76.0/22 Valid None 1 0%low visibility 1
203.72.80.0/21 Valid None 1 0%low visibility 1
203.72.94.0/24 Valid None 1 0%low visibility 1
210.62.247.0/24 Valid None 1 0%low visibility 1
210.243.52.0/23 Valid None 1 0%low visibility 1
210.243.54.0/24 Valid None 1 0%low visibility 1

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
ChangePrefix or setDetailFull-table peers
ROA: origin203.64.36.0/22ROAs covering it name AS1659, not AS17711. If AS17711 should announce it, add a ROA for AS17711.1 of 673
Route object: none203.64.36.0/22No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
ROA: origin210.59.6.0/23ROAs covering it name AS1659, not AS17711. If AS17711 should announce it, add a ROA for AS17711.1 of 673
Route object: none210.59.6.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
ROA: origin210.240.96.0/21ROAs covering it name AS1659, not AS17711. If AS17711 should announce it, add a ROA for AS17711.1 of 673
Route object: none210.240.96.0/21No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
ROA: origin210.240.104.0/24ROAs covering it name AS1659, not AS17711. If AS17711 should announce it, add a ROA for AS17711.1 of 673
Route object: none210.240.104.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
ROA: maxLength134.208.0.0/17ROA 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.1 of 673
Route object: none134.208.0.0/17No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
ROA: maxLength134.208.128.0/17ROA 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.1 of 673
Route object: none134.208.128.0/17No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none163.28.160.0/20No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.64.34.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.64.40.0/22No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.64.76.0/22No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.64.80.0/21No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.68.24.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.68.59.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.68.60.0/22No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.68.72.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.68.153.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.68.154.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.68.200.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.68.210.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.71.0.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.71.58.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.71.60.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.71.244.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.72.48.0/22No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.72.73.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.72.74.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.72.76.0/22No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.72.80.0/21No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none203.72.94.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none210.62.247.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none210.243.52.0/23No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673
Route object: none210.243.54.0/24No route object for it. Add a route object with origin AS17711 in the RIR database for the space.1 of 673

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.