Mirror Details: fi.muni.cz
| Name: | fi.muni.cz |
|---|---|
| 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://ftp.fi.muni.cz/pub/linux/arch/ | http | Czechia | Yes | Yes | 2024-04-25 12:04 | 100.0% | 1:41 | 0.68 | 1.15 | 3.5 | Details |
| http://ftp.linux.cz/pub/linux/arch/ | http | Czechia | Yes | Yes | 2024-04-25 12:04 | 100.0% | 1:41 | 0.44 | 0.82 | 3.0 | Details |
| rsync://ftp.fi.muni.cz/pub/linux/arch/ | rsync | Czechia | Yes | Yes | 2024-04-25 12:04 | 100.0% | 1:41 | 1.71 | 2.22 | 5.6 | Details |
| rsync://ftp.linux.cz/pub/linux/arch/ | rsync | Czechia | Yes | Yes | 2024-04-25 12:04 | 100.0% | 1:41 | 1.79 | 2.25 | 5.7 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| http://ftp.linux.cz/pub/linux/arch/ | http | Czechia | Connection timed out. | 2024-04-20 23:48 | 3 | details |
| rsync://ftp.linux.cz/pub/linux/arch/ | rsync | Czechia | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.2.7] | 2024-04-20 23:48 | 2 | details |
| rsync://ftp.fi.muni.cz/pub/linux/arch/ | rsync | Czechia | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.2.7] | 2024-04-20 23:48 | 1 | details |
| http://ftp.fi.muni.cz/pub/linux/arch/ | http | Czechia | Connection timed out. | 2024-04-20 23:48 | 1 | details |
| rsync://ftp.fi.muni.cz/pub/linux/arch/ | rsync | Czechia | rsync: getaddrinfo: ftp.fi.muni.cz 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7] |
2024-04-20 23:47 | 1 | details |
| http://ftp.fi.muni.cz/pub/linux/arch/ | http | Czechia | Name or service not known | 2024-04-20 23:47 | 1 | details |
| rsync://ftp.linux.cz/pub/linux/arch/ | rsync | Czechia | [Receiver] io timeout after 10 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(200) [Receiver=3.2.7] |
2024-04-20 23:28 | 1 | details |
| rsync://ftp.fi.muni.cz/pub/linux/arch/ | rsync | Czechia | [Receiver] io timeout after 12 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(200) [Receiver=3.2.7] |
2024-04-20 23:28 | 1 | details |
| rsync://ftp.fi.muni.cz/pub/linux/arch/ | rsync | Czechia | [Receiver] io timeout after 10 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(200) [Receiver=3.2.7] |
2024-04-20 23:25 | 1 | details |
| http://ftp.linux.cz/pub/linux/arch/ | http | Czechia | Could not parse time from lastsync | 2024-04-19 08:05 | 13 | details |
| rsync://ftp.linux.cz/pub/linux/arch/ | rsync | Czechia | Could not parse time from lastsync | 2024-04-19 08:05 | 13 | details |
| rsync://ftp.fi.muni.cz/pub/linux/arch/ | rsync | Czechia | Could not parse time from lastsync | 2024-04-19 08:05 | 13 | details |
| http://ftp.fi.muni.cz/pub/linux/arch/ | http | Czechia | Could not parse time from lastsync | 2024-04-19 08:05 | 13 | 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.