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 | unknown | unknown | ∞ | Details | |||
| https://arch.syxpi.fr/arch/ | https | France | Yes | Yes | unknown | unknown | ∞ | Details | |||
| rsync://arch.syxpi.fr/arch/ | rsync | France | Yes | Yes | unknown | unknown | 2.73 | 0.85 | ∞ | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync: [Receiver] failed to connect to arch.syxpi.fr (2a01:e0a:425:1220:be24:11ff:feae:9fd4): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-03-22 21:14 | 50 | details |
| https://arch.syxpi.fr/arch/ | https | France | No route to host | 2026-03-22 21:13 | 100 | details |
| http://arch.syxpi.fr/arch/ | http | France | No route to host | 2026-03-22 21:13 | 100 | 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(139) [Receiver=3.4.1] |
2026-03-22 21:12 | 50 | details |
| http://arch.syxpi.fr/arch/ | http | France | Connection timed out. | 2026-03-19 13:32 | 2 | details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync subprocess killed after 15.0 seconds | 2026-03-19 13:31 | 1 | details |
| https://arch.syxpi.fr/arch/ | https | France | Connection timed out. | 2026-03-19 11:44 | 2 | details |
| rsync://arch.syxpi.fr/arch/ | rsync | France | rsync: [Receiver] failed to connect to arch.syxpi.fr (2a01:e0a:425:1220:be24:11ff:feae:9fd4): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-03-17 13:02 | 5 | details |
| https://arch.syxpi.fr/arch/ | https | France | Connection refused | 2026-03-17 13:01 | 5 | details |
| http://arch.syxpi.fr/arch/ | http | France | Connection refused | 2026-03-17 13:01 | 5 | 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(139) [Receiver=3.4.1] |
2026-03-17 13:00 | 5 | details |
| https://arch.syxpi.fr/arch/ | https | France | HTTP Error 502: Bad Gateway | 2026-03-17 12:59 | 5 | details |
| http://arch.syxpi.fr/arch/ | http | France | HTTP Error 502: Bad Gateway | 2026-03-17 12:59 | 5 | details |
| https://arch.syxpi.fr/arch/ | https | France | [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1081) | 2026-03-17 09:48 | 26 | details |
| http://arch.syxpi.fr/arch/ | http | France | [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1081) | 2026-03-17 09:48 | 26 | 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.