Mirror Details: leitecastro.com
| Name: | leitecastro.com |
|---|---|
| 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://mirror.leitecastro.com/archlinux/ | http | Portugal | Yes | Yes | unknown | unknown | ∞ | Details | |||
| https://mirror.leitecastro.com/archlinux/ | https | Portugal | Yes | Yes | unknown | unknown | ∞ | Details | |||
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | Yes | Yes | unknown | unknown | 0.29 | 0.40 | ∞ | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | rsync: [Receiver] failed to connect to mirror.leitecastro.com (2602:faa5:189::): No route to host (113) rsync: [Receiver] failed to connect to mirror.leitecastro.com (2602:faa5:190::): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(165) [Receiver=3.5.0-g471e17dc] |
2026-08-18 01:09 | 30 | details |
| http://mirror.leitecastro.com/archlinux/ | http | Portugal | No route to host | 2026-08-18 01:09 | 395 | details |
| https://mirror.leitecastro.com/archlinux/ | https | Portugal | No route to host | 2026-08-18 01:09 | 387 | details |
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | rsync: [Receiver] failed to connect to mirror.leitecastro.com (23.147.168.189): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(165) [Receiver=3.5.0-g471e17dc] |
2026-08-18 01:07 | 42 | details |
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | rsync error: timeout waiting for daemon connection (code 35) at socket.c(429) [Receiver=3.5.0-g471e17dc] | 2026-08-18 01:03 | 59 | details |
| http://mirror.leitecastro.com/archlinux/ | http | Portugal | Connection timed out. | 2026-08-18 01:02 | 275 | details |
| https://mirror.leitecastro.com/archlinux/ | https | Portugal | Connection timed out. | 2026-08-18 01:02 | 283 | details |
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | rsync: [Receiver] failed to connect to mirror.leitecastro.com (2602:faa5:190::): No route to host (113) rsync: [Receiver] failed to connect to mirror.leitecastro.com (2602:faa5:189::): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(165) [Receiver=3.5.0-g471e17dc] |
2026-08-17 23:11 | 21 | details |
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | rsync: [Receiver] failed to connect to mirror.leitecastro.com (2602:faa5:190::): No route to host (113) rsync: [Receiver] failed to connect to mirror.leitecastro.com (2602:faa5:189::): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.4] |
2026-08-16 11:34 | 94 | details |
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | rsync: [Receiver] failed to connect to mirror.leitecastro.com (23.147.168.189): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.4] |
2026-08-16 11:32 | 132 | details |
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | rsync error: timeout waiting for daemon connection (code 35) at socket.c(282) [Receiver=3.4.4] | 2026-08-16 11:04 | 217 | details |
| rsync://mirror.leitecastro.com/archlinux/ | rsync | Portugal | rsync: [Receiver] failed to connect to mirror.leitecastro.com (2602:faa5:189::): No route to host (113) rsync: [Receiver] failed to connect to mirror.leitecastro.com (2602:faa5:190::): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.4] |
2026-08-16 09:44 | 76 | details |
| http://mirror.leitecastro.com/archlinux/ | http | Portugal | Name or service not known | 2026-08-11 07:40 | 1 | details |
| https://mirror.leitecastro.com/archlinux/ | https | Portugal | Name or service not known | 2026-08-11 07:40 | 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.