Mirror Details: flokinet.net
| Name: | flokinet.net |
|---|---|
| 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://is.mirror.flokinet.net/archlinux/ | http | Iceland | Yes | Yes | 2024-05-13 21:45 | 100.0% | 2:59 | 0.42 | 0.50 | 3.9 | Details |
| http://nl.mirror.flokinet.net/archlinux/ | http | Netherlands | Yes | Yes | 2024-05-13 22:14 | 100.0% | 2:12 | 0.31 | 0.39 | 2.9 | Details |
| http://ro.mirror.flokinet.net/archlinux/ | http | Romania | Yes | Yes | 2024-05-13 21:29 | 100.0% | 3:00 | 0.47 | 0.58 | 4.1 | Details |
| https://is.mirror.flokinet.net/archlinux/ | https | Iceland | Yes | Yes | 2024-05-13 21:45 | 100.0% | 2:59 | 0.50 | 0.57 | 4.1 | Details |
| https://nl.mirror.flokinet.net/archlinux/ | https | Netherlands | Yes | Yes | 2024-05-13 22:14 | 100.0% | 2:12 | 0.33 | 0.45 | 3.0 | Details |
| https://ro.mirror.flokinet.net/archlinux/ | https | Romania | Yes | Yes | 2024-05-13 21:29 | 100.0% | 3:00 | 0.52 | 0.75 | 4.3 | Details |
| rsync://is.mirror.flokinet.net/archlinux/ | rsync | Iceland | Yes | Yes | 2024-05-13 21:45 | 100.0% | 2:59 | 2.20 | 1.67 | 6.8 | Details |
| rsync://nl.mirror.flokinet.net/archlinux/ | rsync | Netherlands | Yes | Yes | unknown | unknown | 0.80 | 0.56 | ∞ | Details | |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | Yes | Yes | 2024-05-13 21:29 | 100.0% | 3:00 | 3.69 | 2.18 | 8.9 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| rsync://nl.mirror.flokinet.net/archlinux/ | rsync | Netherlands | @ERROR: invalid gid nogroup rsync error: error starting client-server protocol (code 5) at main.c(1850) [Receiver=3.3.0] |
2024-05-13 23:14 | 1353 | details |
| rsync://is.mirror.flokinet.net/archlinux/ | rsync | Iceland | Could not parse time from lastsync | 2024-05-12 06:48 | 24 | details |
| https://is.mirror.flokinet.net/archlinux/ | https | Iceland | Could not parse time from lastsync | 2024-05-12 06:48 | 24 | details |
| http://is.mirror.flokinet.net/archlinux/ | http | Iceland | Could not parse time from lastsync | 2024-05-12 06:48 | 24 | details |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | Could not parse time from lastsync | 2024-05-12 06:36 | 22 | details |
| https://ro.mirror.flokinet.net/archlinux/ | https | Romania | Could not parse time from lastsync | 2024-05-12 06:36 | 22 | details |
| http://ro.mirror.flokinet.net/archlinux/ | http | Romania | Could not parse time from lastsync | 2024-05-12 06:36 | 22 | details |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | [Receiver] io timeout after 13 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(200) [Receiver=3.3.0] |
2024-05-11 08:11 | 1 | details |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | rsync: getaddrinfo: ro.mirror.flokinet.net 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-05-10 09:15 | 1 | details |
| rsync://nl.mirror.flokinet.net/archlinux/ | rsync | Netherlands | rsync: getaddrinfo: nl.mirror.flokinet.net 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-05-09 23:40 | 1 | details |
| https://nl.mirror.flokinet.net/archlinux/ | https | Netherlands | Name or service not known | 2024-05-09 23:40 | 1 | details |
| http://nl.mirror.flokinet.net/archlinux/ | http | Netherlands | Name or service not known | 2024-05-09 23:40 | 1 | details |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | [Receiver] io timeout after 10 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(200) [Receiver=3.3.0] |
2024-05-09 01:20 | 1 | details |
| https://is.mirror.flokinet.net/archlinux/ | https | Iceland | Connection timed out. | 2024-05-07 16:39 | 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.