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 17:19 | 100.0% | 0:33 | 0.27 | 0.70 | 1.5 | Details |
| http://mirror.dal10.us.leaseweb.net/archlinux/ | http | United States | Yes | Yes | 2024-05-19 17:20 | 100.0% | 0:35 | 0.34 | 0.42 | 1.4 | Details |
| http://mirror.fra10.de.leaseweb.net/archlinux/ | http | Germany | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:33 | 0.27 | 0.51 | 1.3 | Details |
| http://mirror.mia11.us.leaseweb.net/archlinux/ | http | United States | Yes | Yes | 2024-05-19 17:20 | 100.0% | 0:34 | 0.33 | 0.27 | 1.2 | Details |
| http://mirror.sfo12.us.leaseweb.net/archlinux/ | http | United States | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:32 | 0.43 | 0.34 | 1.3 | Details |
| http://mirror.wdc1.us.leaseweb.net/archlinux/ | http | United States | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:34 | 0.23 | 0.18 | 1.0 | Details |
| https://mirror.ams1.nl.leaseweb.net/archlinux/ | https | Netherlands | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:32 | 0.67 | 1.47 | 2.7 | Details |
| https://mirror.dal10.us.leaseweb.net/archlinux/ | https | United States | Yes | Yes | 2024-05-19 17:20 | 100.0% | 0:35 | 0.76 | 0.60 | 2.0 | Details |
| https://mirror.fra10.de.leaseweb.net/archlinux/ | https | Germany | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:33 | 0.62 | 0.94 | 2.1 | Details |
| https://mirror.mia11.us.leaseweb.net/archlinux/ | https | United States | Yes | Yes | 2024-05-19 17:20 | 100.0% | 0:35 | 0.64 | 0.49 | 1.7 | Details |
| https://mirror.sfo12.us.leaseweb.net/archlinux/ | https | United States | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:32 | 0.61 | 0.25 | 1.4 | Details |
| https://mirror.wdc1.us.leaseweb.net/archlinux/ | https | United States | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:33 | 0.59 | 0.50 | 1.6 | Details |
| rsync://mirror.ams1.nl.leaseweb.net/archlinux/ | rsync | Netherlands | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:33 | 2.05 | 2.44 | 5.1 | Details |
| rsync://mirror.dal10.us.leaseweb.net/archlinux/ | rsync | United States | Yes | Yes | 2024-05-19 17:20 | 100.0% | 0:34 | 1.92 | 0.86 | 3.4 | Details |
| rsync://mirror.fra10.de.leaseweb.net/archlinux/ | rsync | Germany | Yes | Yes | 2024-05-19 17:19 | 66.9% | 0:33 | 1.64 | 2.19 | 6.6 | Details |
| rsync://mirror.mia11.us.leaseweb.net/archlinux/ | rsync | United States | Yes | Yes | 2024-05-19 17:20 | 100.0% | 0:35 | 2.01 | 1.04 | 3.6 | Details |
| rsync://mirror.sfo12.us.leaseweb.net/archlinux/ | rsync | United States | Yes | Yes | 2024-05-19 17:19 | 100.0% | 0:32 | 2.43 | 0.75 | 3.7 | Details |
| rsync://mirror.wdc1.us.leaseweb.net/archlinux/ | rsync | United States | Yes | Yes | 2024-05-19 17:19 | 36.6% | 0:33 | 1.12 | 0.82 | 6.8 | 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 17:48 | 825 | 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 17:09 | 435 | 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.