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-17 06:15 | 97.3% | 2:02 | 0.44 | 0.53 | 3.1 | Details |
| http://nl.mirror.flokinet.net/archlinux/ | http | Netherlands | Yes | Yes | 2024-05-17 07:44 | 100.0% | 1:50 | 0.37 | 0.57 | 2.8 | Details |
| http://ro.mirror.flokinet.net/archlinux/ | http | Romania | Yes | Yes | 2024-05-17 06:15 | 100.0% | 2:01 | 0.52 | 0.72 | 3.3 | Details |
| https://is.mirror.flokinet.net/archlinux/ | https | Iceland | Yes | Yes | 2024-05-17 06:15 | 97.3% | 2:02 | 0.55 | 0.76 | 3.5 | Details |
| https://nl.mirror.flokinet.net/archlinux/ | https | Netherlands | Yes | Yes | 2024-05-17 07:44 | 100.0% | 1:50 | 0.37 | 0.58 | 2.8 | Details |
| https://ro.mirror.flokinet.net/archlinux/ | https | Romania | Yes | Yes | 2024-05-17 06:15 | 99.5% | 2:02 | 0.57 | 0.81 | 3.4 | Details |
| rsync://is.mirror.flokinet.net/archlinux/ | rsync | Iceland | Yes | Yes | 2024-05-17 06:15 | 97.3% | 2:02 | 2.91 | 2.19 | 7.3 | Details |
| rsync://nl.mirror.flokinet.net/archlinux/ | rsync | Netherlands | Yes | Yes | unknown | unknown | 0.79 | 0.58 | ∞ | Details | |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | Yes | Yes | 2024-05-17 06:15 | 100.0% | 2:01 | 3.68 | 2.27 | 8.0 | 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-17 09:17 | 1353 | details |
| rsync://is.mirror.flokinet.net/archlinux/ | rsync | Iceland | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] | 2024-05-17 00:36 | 18 | details |
| https://is.mirror.flokinet.net/archlinux/ | https | Iceland | Connection timed out. | 2024-05-17 00:36 | 18 | details |
| http://is.mirror.flokinet.net/archlinux/ | http | Iceland | Connection timed out. | 2024-05-17 00:36 | 18 | details |
| https://ro.mirror.flokinet.net/archlinux/ | https | Romania | Connection timed out. | 2024-05-16 09:54 | 1 | details |
| rsync://is.mirror.flokinet.net/archlinux/ | rsync | Iceland | Could not parse time from lastsync | 2024-05-14 15:46 | 48 | details |
| https://is.mirror.flokinet.net/archlinux/ | https | Iceland | Could not parse time from lastsync | 2024-05-14 15:46 | 48 | details |
| http://is.mirror.flokinet.net/archlinux/ | http | Iceland | Could not parse time from lastsync | 2024-05-14 15:46 | 48 | details |
| rsync://nl.mirror.flokinet.net/archlinux/ | rsync | Netherlands | rsync: [Receiver] failed to connect to nl.mirror.flokinet.net (2a06:1700:3:12::12): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-05-14 13:22 | 1 | details |
| https://nl.mirror.flokinet.net/archlinux/ | https | Netherlands | Connection timed out. | 2024-05-14 13:22 | 1 | details |
| http://nl.mirror.flokinet.net/archlinux/ | http | Netherlands | Connection timed out. | 2024-05-14 13:22 | 1 | 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 |
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.