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-04-23 16:19 100.0% 0:33 0.22 0.43 1.2 Details
http://mirror.dal10.us.leaseweb.net/archlinux/ http United States Yes Yes 2024-04-23 16:19 100.0% 0:33 0.29 0.37 1.2 Details
http://mirror.fra10.de.leaseweb.net/archlinux/ http Germany Yes Yes 2024-04-23 16:21 100.0% 0:33 0.28 0.49 1.3 Details
http://mirror.mia11.us.leaseweb.net/archlinux/ http United States Yes Yes 2024-04-23 16:19 100.0% 0:33 0.35 0.31 1.2 Details
http://mirror.sfo12.us.leaseweb.net/archlinux/ http United States Yes Yes 2024-04-23 16:19 100.0% 0:33 0.42 0.35 1.3 Details
http://mirror.wdc1.us.leaseweb.net/archlinux/ http United States Yes Yes 2024-04-23 16:19 100.0% 0:33 0.24 0.31 1.1 Details
https://mirror.ams1.nl.leaseweb.net/archlinux/ https Netherlands Yes Yes 2024-04-23 16:19 100.0% 0:33 0.54 0.81 1.9 Details
https://mirror.dal10.us.leaseweb.net/archlinux/ https United States Yes Yes 2024-04-23 16:19 100.0% 0:33 0.73 0.57 1.9 Details
https://mirror.fra10.de.leaseweb.net/archlinux/ https Germany Yes Yes 2024-04-23 16:21 100.0% 0:33 0.63 0.89 2.1 Details
https://mirror.mia11.us.leaseweb.net/archlinux/ https United States Yes Yes 2024-04-23 16:19 100.0% 0:33 0.66 0.45 1.7 Details
https://mirror.sfo12.us.leaseweb.net/archlinux/ https United States Yes Yes 2024-04-23 16:19 100.0% 0:33 0.64 0.29 1.5 Details
https://mirror.wdc1.us.leaseweb.net/archlinux/ https United States Yes Yes 2024-04-23 16:19 100.0% 0:32 0.62 0.70 1.9 Details
rsync://mirror.ams1.nl.leaseweb.net/archlinux/ rsync Netherlands Yes Yes 2024-04-23 14:19 69.7% 0:32 1.74 2.05 6.2 Details
rsync://mirror.dal10.us.leaseweb.net/archlinux/ rsync United States Yes Yes 2024-04-23 16:19 100.0% 0:33 1.92 0.96 3.4 Details
rsync://mirror.fra10.de.leaseweb.net/archlinux/ rsync Germany Yes Yes 2024-04-23 16:21 7.9% 0:33 0.96 1.10 33.1 Details
rsync://mirror.mia11.us.leaseweb.net/archlinux/ rsync United States Yes Yes 2024-04-23 16:19 100.0% 0:33 2.01 0.98 3.5 Details
rsync://mirror.sfo12.us.leaseweb.net/archlinux/ rsync United States Yes Yes 2024-04-23 16:19 100.0% 0:33 2.60 0.95 4.1 Details
rsync://mirror.wdc1.us.leaseweb.net/archlinux/ rsync United States Yes Yes unknown unknown 0.78 0.60 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-04-23 17:04 186 details
rsync://mirror.ams1.nl.leaseweb.net/archlinux/ rsync Netherlands @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-04-23 17:04 56 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-04-23 15:09 172 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(1859) [Receiver=3.2.7]
2024-04-22 17:27 508 details
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(1859) [Receiver=3.2.7]
2024-04-22 17:26 580 details
rsync://mirror.ams1.nl.leaseweb.net/archlinux/ rsync Netherlands @ERROR: max connections (20) reached -- try again later
rsync error: error starting client-server protocol (code 5) at main.c(1859) [Receiver=3.2.7]
2024-04-22 17:26 252 details
https://mirror.ams1.nl.leaseweb.net/archlinux/ https Netherlands Connection timed out. 2024-04-22 13:58 3 details
https://mirror.fra10.de.leaseweb.net/archlinux/ https Germany Connection timed out. 2024-04-21 04:25 3 details
rsync://mirror.fra10.de.leaseweb.net/archlinux/ rsync Germany [Receiver] io timeout after 10 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(200) [Receiver=3.2.7]
2024-04-21 04:22 1 details
https://mirror.wdc1.us.leaseweb.net/archlinux/ https United States Could not parse time from lastsync 2024-04-19 20:20 6 details
http://mirror.wdc1.us.leaseweb.net/archlinux/ http United States Could not parse time from lastsync 2024-04-19 20:18 6 details
rsync://mirror.wdc1.us.leaseweb.net/archlinux/ rsync United States Could not parse time from lastsync 2024-04-19 20:18 6 details
http://mirror.wdc1.us.leaseweb.net/archlinux/ http United States Connection timed out. 2024-04-18 04:58 2 details
rsync://mirror.wdc1.us.leaseweb.net/archlinux/ rsync United States rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.2.7] 2024-04-18 04:58 2 details
https://mirror.wdc1.us.leaseweb.net/archlinux/ https United States Connection timed out. 2024-04-18 04:57 1 details
rsync://mirror.fra10.de.leaseweb.net/archlinux/ rsync Germany rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.2.7] 2024-04-18 04:41 1 details
http://mirror.fra10.de.leaseweb.net/archlinux/ http Germany Connection timed out. 2024-04-18 04:40 1 details
rsync://mirror.fra10.de.leaseweb.net/archlinux/ rsync Germany rsync: [Receiver] failed to connect to mirror.fra10.de.leaseweb.net (37.58.58.140): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]
2024-04-18 04:39 1 details
http://mirror.fra10.de.leaseweb.net/archlinux/ http Germany Connection refused 2024-04-18 04:37 1 details
https://mirror.fra10.de.leaseweb.net/archlinux/ https Germany Connection refused 2024-04-18 04:37 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.