Mirror Details: syxpi.fr
| Name: | syxpi.fr |
|---|---|
| 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://arch.syxpi.fr/arch/ | http | France | Yes | Yes | 2026-06-13 01:02 | 91.7% | 1:22 | 0.27 | 0.54 | 2.4 | Details |
| https://arch.syxpi.fr/arch/ | https | France | Yes | Yes | 2026-06-13 01:02 | 91.7% | 1:22 | 0.15 | 0.30 | 2.0 | Details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | Yes | Yes | 2026-06-13 01:02 | 91.7% | 1:23 | 0.62 | 0.48 | 2.7 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync: [sender] link_stat "/lastsync" (in arch) failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1867) [Receiver=3.4.3] |
2026-06-12 16:46 | 2 | details |
| https://arch.syxpi.fr/arch/ | https | France | HTTP Error 404: Not Found | 2026-06-12 16:46 | 4 | details |
| http://arch.syxpi.fr/arch/ | http | France | HTTP Error 404: Not Found | 2026-06-12 16:46 | 4 | details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync: [sender] link_stat "/lastsync" (in arch) failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1867) [Receiver=3.4.3] rsync: [Receiver] read error: Connection reset by peer (104) |
2026-06-12 16:00 | 2 | details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync: [Receiver] failed to connect to arch.syxpi.fr (2a01:e0a:909:b210:be24:11ff:feae:9fd4): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
2026-06-12 15:30 | 163 | details |
| https://arch.syxpi.fr/arch/ | https | France | No route to host | 2026-06-12 15:29 | 180 | details |
| http://arch.syxpi.fr/arch/ | http | France | No route to host | 2026-06-12 15:29 | 180 | details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync: [Receiver] failed to connect to arch.syxpi.fr (82.67.51.130): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
2026-06-12 15:28 | 2 | details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync: [Receiver] failed to connect to arch.syxpi.fr (2a01:e0a:909:b210:be24:11ff:feae:9fd4): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
2026-06-12 15:27 | 1 | details |
| https://arch.syxpi.fr/arch/ | https | France | HTTP Error 502: Bad Gateway | 2026-06-12 15:27 | 2 | details |
| http://arch.syxpi.fr/arch/ | http | France | HTTP Error 502: Bad Gateway | 2026-06-12 15:27 | 2 | details |
| https://arch.syxpi.fr/arch/ | https | France | Connection refused | 2026-06-12 15:27 | 1 | details |
| http://arch.syxpi.fr/arch/ | http | France | Connection refused | 2026-06-12 15:27 | 1 | details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync error: timeout waiting for daemon connection (code 35) at socket.c(282) [Receiver=3.4.3] | 2026-06-09 15:16 | 2 | details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync: [Receiver] failed to connect to arch.syxpi.fr (82.67.51.130): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
2026-06-09 14:46 | 160 | details |
| https://arch.syxpi.fr/arch/ | https | France | [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1081) | 2026-06-09 10:31 | 1 | details |
| https://arch.syxpi.fr/arch/ | https | France | [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1081) | 2026-06-09 09:29 | 145 | details |
| http://arch.syxpi.fr/arch/ | http | France | [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1081) | 2026-06-09 09:29 | 145 | 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.