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 | 2025-03-01 15:46 | 100.0% | 2:12 | 0.40 | 0.34 | 2.9 | Details |
| http://nl.mirror.flokinet.net/archlinux/ | http | Netherlands | Yes | Yes | 2025-03-01 14:45 | 100.0% | 2:05 | 0.34 | 0.42 | 2.8 | Details |
| http://ro.mirror.flokinet.net/archlinux/ | http | Romania | Yes | Yes | 2025-03-01 13:15 | 100.0% | 2:30 | 0.40 | 0.42 | 3.3 | Details |
| https://is.mirror.flokinet.net/archlinux/ | https | Iceland | Yes | Yes | 2025-03-01 15:46 | 100.0% | 2:12 | 0.42 | 0.35 | 3.0 | Details |
| https://nl.mirror.flokinet.net/archlinux/ | https | Netherlands | Yes | Yes | 2025-03-01 14:45 | 100.0% | 2:05 | 0.36 | 0.48 | 2.9 | Details |
| https://ro.mirror.flokinet.net/archlinux/ | https | Romania | Yes | Yes | 2025-03-01 13:15 | 99.3% | 2:31 | 0.45 | 0.45 | 3.4 | Details |
| rsync://is.mirror.flokinet.net/archlinux/ | rsync | Iceland | Yes | Yes | 2025-03-01 15:46 | 100.0% | 2:12 | 2.01 | 1.06 | 5.3 | Details |
| rsync://nl.mirror.flokinet.net/archlinux/ | rsync | Netherlands | Yes | Yes | 2025-03-01 14:45 | 100.0% | 2:05 | 1.72 | 1.45 | 5.3 | Details |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | Yes | Yes | 2025-03-01 13:15 | 99.3% | 2:31 | 4.78 | 2.42 | 9.8 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | [Receiver] io timeout after 15 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-28 23:51 | 1 | details |
| https://ro.mirror.flokinet.net/archlinux/ | https | Romania | Connection timed out. | 2025-02-28 23:51 | 6 | details |
| http://ro.mirror.flokinet.net/archlinux/ | http | Romania | Connection timed out. | 2025-02-28 08:54 | 3 | details |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | [Receiver] io timeout after 11 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-28 07:10 | 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(201) [Receiver=3.4.1] |
2025-02-28 03:35 | 2 | details |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | 2025-02-27 20:40 | 1 | details |
| rsync://ro.mirror.flokinet.net/archlinux/ | rsync | Romania | [Receiver] io timeout after 12 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-27 18:29 | 1 | 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.4.1] |
2025-02-26 20:56 | 270 | details |
| https://nl.mirror.flokinet.net/archlinux/ | https | Netherlands | No route to host | 2025-02-26 20:56 | 606 | details |
| http://nl.mirror.flokinet.net/archlinux/ | http | Netherlands | No route to host | 2025-02-26 20:56 | 607 | details |
| rsync://nl.mirror.flokinet.net/archlinux/ | rsync | Netherlands | rsync: [Receiver] failed to connect to nl.mirror.flokinet.net (185.246.188.7): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2025-02-26 20:53 | 337 | details |
| https://nl.mirror.flokinet.net/archlinux/ | https | Netherlands | Connection timed out. | 2025-02-25 21:26 | 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.