Mirror Details: ccns.ncku.edu.tw
| Name: | ccns.ncku.edu.tw |
|---|---|
| Tier: | Tier 2 |
| Has ISOs: | Yes |
Available URLs
| Mirror URL | Protocol | Country | IPv4 | IPv6 | Last Sync | Completion % | μ Delay (hh:mm) | μ Duration (s) | σ Duration (s) | Score | Details |
|---|---|---|---|---|---|---|---|---|---|---|---|
| http://archlinux.ccns.ncku.edu.tw/archlinux/ | http | Taiwan | Yes | No | 2026-10-10 16:49 | 100.0% | 0:21 | 1.73 | 1.74 | 3.8 | Details |
| https://archlinux.ccns.ncku.edu.tw/archlinux/ | https | Taiwan | Yes | No | 2026-10-10 16:49 | 100.0% | 0:22 | 2.85 | 1.57 | 4.8 | Details |
| rsync://archlinux.ccns.ncku.edu.tw/archlinux/ | rsync | Taiwan | Yes | No | 2026-10-10 16:49 | 100.0% | 0:22 | 5.35 | 1.49 | 7.2 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| http://archlinux.ccns.ncku.edu.tw/archlinux/ | http | Taiwan | Name or service not known | 2026-10-09 10:59 | 1 | details |
| rsync://archlinux.ccns.ncku.edu.tw/archlinux/ | rsync | Taiwan | rsync: getaddrinfo: archlinux.ccns.ncku.edu.tw 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(165) [Receiver=3.5.1-g04355d27] |
2026-10-08 10:10 | 1 | details |
| rsync://archlinux.ccns.ncku.edu.tw/archlinux/ | rsync | Taiwan | rsync subprocess killed after 15.0 seconds | 2026-10-06 19:31 | 1 | details |
| rsync://archlinux.ccns.ncku.edu.tw/archlinux/ | rsync | Taiwan | rsync: getaddrinfo: archlinux.ccns.ncku.edu.tw 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(165) [Receiver=3.5.0-g471e17dc] |
2026-10-06 03:05 | 1 | details |
| https://archlinux.ccns.ncku.edu.tw/archlinux/ | https | Taiwan | Name or service not known | 2026-10-06 03:05 | 1 | details |
| https://archlinux.ccns.ncku.edu.tw/archlinux/ | https | Taiwan | [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1082) | 2026-10-05 16:59 | 1 | details |
Mirror Status Charts
Periodic checks of the mirrors are done from various geographic locations, IP addresses, and using IPv4 or IPv6. These results are summarized in graphical form below.