Mirror Details: leaseweb.net
Name: | leaseweb.net |
---|---|
Tier: | Tier 1 |
Has ISOs: | Yes |
Available URLs
Mirror URL | Protocol | Country | IPv4 | IPv6 | Last Sync | Completion % | μ Delay (hh:mm) | μ Duration (s) | σ Duration (s) | Score | Details |
---|---|---|---|---|---|---|---|---|---|---|---|
http://mirror.ams1.nl.leaseweb.net/archlinux/ | http | Netherlands | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:32 | 0.27 | 0.83 | 1.6 | Details |
http://mirror.dal10.us.leaseweb.net/archlinux/ | http | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:34 | 0.33 | 0.42 | 1.3 | Details |
http://mirror.fra10.de.leaseweb.net/archlinux/ | http | Germany | Yes | Yes | 2024-05-19 01:20 | 100.0% | 0:31 | 0.27 | 0.48 | 1.3 | Details |
http://mirror.mia11.us.leaseweb.net/archlinux/ | http | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:34 | 0.33 | 0.36 | 1.3 | Details |
http://mirror.sfo12.us.leaseweb.net/archlinux/ | http | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:32 | 0.45 | 0.44 | 1.4 | Details |
http://mirror.wdc1.us.leaseweb.net/archlinux/ | http | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:32 | 0.26 | 0.32 | 1.1 | Details |
https://mirror.ams1.nl.leaseweb.net/archlinux/ | https | Netherlands | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:31 | 0.66 | 1.35 | 2.5 | Details |
https://mirror.dal10.us.leaseweb.net/archlinux/ | https | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:34 | 0.73 | 0.58 | 1.9 | Details |
https://mirror.fra10.de.leaseweb.net/archlinux/ | https | Germany | Yes | Yes | 2024-05-19 01:20 | 100.0% | 0:31 | 0.63 | 0.91 | 2.1 | Details |
https://mirror.mia11.us.leaseweb.net/archlinux/ | https | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:34 | 0.63 | 0.45 | 1.7 | Details |
https://mirror.sfo12.us.leaseweb.net/archlinux/ | https | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:32 | 0.65 | 0.37 | 1.6 | Details |
https://mirror.wdc1.us.leaseweb.net/archlinux/ | https | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:31 | 0.62 | 0.44 | 1.6 | Details |
rsync://mirror.ams1.nl.leaseweb.net/archlinux/ | rsync | Netherlands | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:32 | 2.13 | 2.89 | 5.6 | Details |
rsync://mirror.dal10.us.leaseweb.net/archlinux/ | rsync | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:34 | 1.88 | 0.87 | 3.3 | Details |
rsync://mirror.fra10.de.leaseweb.net/archlinux/ | rsync | Germany | Yes | Yes | 2024-05-19 01:20 | 25.4% | 0:41 | 1.19 | 1.38 | 12.9 | Details |
rsync://mirror.mia11.us.leaseweb.net/archlinux/ | rsync | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:34 | 1.91 | 0.95 | 3.4 | Details |
rsync://mirror.sfo12.us.leaseweb.net/archlinux/ | rsync | United States | Yes | Yes | 2024-05-19 01:19 | 100.0% | 0:32 | 2.40 | 0.74 | 3.7 | Details |
rsync://mirror.wdc1.us.leaseweb.net/archlinux/ | rsync | United States | Yes | Yes | 2024-05-19 00:19 | 67.2% | 0:31 | 1.52 | 1.08 | 4.7 | Details |
Error Log
Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
---|---|---|---|---|---|---|
rsync://mirror.wdc1.us.leaseweb.net/archlinux/ | rsync | United States | @ERROR: max connections (20) reached -- try again later rsync error: error starting client-server protocol (code 5) at main.c(1850) [Receiver=3.3.0] |
2024-05-19 01:47 | 864 | details |
rsync://mirror.fra10.de.leaseweb.net/archlinux/ | rsync | Germany | @ERROR: max connections (20) reached -- try again later rsync error: error starting client-server protocol (code 5) at main.c(1850) [Receiver=3.3.0] |
2024-05-19 01:36 | 429 | details |
rsync://mirror.fra10.de.leaseweb.net/archlinux/ | rsync | Germany | Could not parse time from lastsync | 2024-05-17 03:20 | 11 | details |
https://mirror.sfo12.us.leaseweb.net/archlinux/ | https | United States | Could not parse time from lastsync | 2024-05-17 03:19 | 11 | details |
http://mirror.sfo12.us.leaseweb.net/archlinux/ | http | United States | Could not parse time from lastsync | 2024-05-17 03:19 | 11 | details |
rsync://mirror.sfo12.us.leaseweb.net/archlinux/ | rsync | United States | Could not parse time from lastsync | 2024-05-17 03:18 | 10 | details |
http://mirror.fra10.de.leaseweb.net/archlinux/ | http | Germany | Could not parse time from lastsync | 2024-05-17 03:18 | 10 | details |
https://mirror.fra10.de.leaseweb.net/archlinux/ | https | Germany | Could not parse time from lastsync | 2024-05-17 03:18 | 10 | details |
rsync://mirror.dal10.us.leaseweb.net/archlinux/ | rsync | United States | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] | 2024-05-16 04:57 | 1 | details |
http://mirror.mia11.us.leaseweb.net/archlinux/ | http | United States | Connection refused | 2024-05-16 04:56 | 1 | details |
rsync://mirror.mia11.us.leaseweb.net/archlinux/ | rsync | United States | rsync: [Receiver] failed to connect to mirror.mia11.us.leaseweb.net (2607:f5b6:1:48::211): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-05-16 04:56 | 1 | details |
https://mirror.mia11.us.leaseweb.net/archlinux/ | https | United States | Connection refused | 2024-05-16 04:56 | 1 | details |
http://mirror.dal10.us.leaseweb.net/archlinux/ | http | United States | Connection refused | 2024-05-16 04:55 | 1 | details |
https://mirror.dal10.us.leaseweb.net/archlinux/ | https | United States | Connection refused | 2024-05-16 04:55 | 1 | details |
rsync://mirror.sfo12.us.leaseweb.net/archlinux/ | rsync | United States | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] | 2024-05-16 04:53 | 1 | details |
https://mirror.ams1.nl.leaseweb.net/archlinux/ | https | Netherlands | Connection refused | 2024-05-16 04:36 | 1 | details |
https://mirror.fra10.de.leaseweb.net/archlinux/ | https | Germany | Connection timed out. | 2024-05-14 09:53 | 1 | details |
https://mirror.sfo12.us.leaseweb.net/archlinux/ | https | United States | Connection timed out. | 2024-05-13 17:31 | 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.