Network · data from 2026-11-12
AS17712 CCU-TW - National Chung Cheng University
Registry name: CCU-TW - National Chung Cheng University, TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17712, 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.
| 140.123.0.0/16 | Valid | Other origin only | 1 0%low visibility |
| 140.125.0.0/16 | Valid | Other origin only | 1 0%low visibility |
| 192.192.131.0/24 | Valid | None | 1 0%low visibility |
| 203.64.22.0/24 | Valid | None | 1 0%low visibility |
| 203.72.0.0/21 | Valid | None | 1 0%low visibility |
| 203.72.20.0/24 | Valid | None | 1 0%low visibility |
| 210.60.205.0/24 | Valid | None | 1 0%low visibility |
| 210.60.206.0/24 | Valid | None | 1 0%low visibility |
| 210.70.9.0/24 | Valid | None | 1 0%low visibility |
| 210.70.187.0/24 | Valid | None | 1 0%low visibility |
| 210.70.188.0/24 | Valid | None | 1 0%low visibility |
| 210.240.202.0/23 | Valid | None | 1 0%low visibility |
AS-SET
AS17712 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 12 are in fix.csv.
- Route object: none12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 140.123.0.0/16 | Route objects for it name AS9505. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 140.125.0.0/16 | Route objects for it name AS9505. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 192.192.131.0/24 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 203.64.22.0/24 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 203.72.0.0/21 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 203.72.20.0/24 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 210.60.205.0/24 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 210.60.206.0/24 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 210.70.9.0/24 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 210.70.187.0/24 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 210.70.188.0/24 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
| Route object: none | 210.240.202.0/23 | No route object for it. Add a route object with origin AS17712 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS17712 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.