Mirror Details: shibe.party
| Name: | shibe.party |
|---|---|
| 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://de.mirror.shibe.party/archlinux/ | http | Germany | Yes | Yes | 2026-05-21 10:21 | 99.0% | 0:30 | 0.06 | 0.08 | 0.7 | Details |
| http://fr.mirror.shibe.party/archlinux/ | http | France | Yes | No | 2026-05-21 10:27 | 100.0% | 0:31 | 0.11 | 0.07 | 0.7 | Details |
| https://de.mirror.shibe.party/archlinux/ | https | Germany | Yes | Yes | 2026-05-21 10:21 | 99.0% | 0:30 | 0.07 | 0.06 | 0.6 | Details |
| https://fr.mirror.shibe.party/archlinux/ | https | France | Yes | No | 2026-05-21 10:27 | 100.0% | 0:31 | 0.19 | 0.09 | 0.8 | Details |
| rsync://de.mirror.shibe.party/archlinux/ | rsync | Germany | Yes | Yes | 2026-05-21 10:21 | 98.0% | 0:30 | 0.56 | 0.30 | 1.4 | Details |
| rsync://fr.mirror.shibe.party/archlinux/ | rsync | France | Yes | No | 2026-05-21 10:27 | 100.0% | 0:31 | 0.69 | 0.75 | 2.0 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| https://de.mirror.shibe.party/archlinux/ | https | Germany | Connection timed out. | 2026-05-20 18:22 | 1 | details |
| http://de.mirror.shibe.party/archlinux/ | http | Germany | Connection timed out. | 2026-05-20 18:22 | 1 | details |
| rsync://de.mirror.shibe.party/archlinux/ | rsync | Germany | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.2] | 2026-05-20 18:22 | 1 | details |
| rsync://de.mirror.shibe.party/archlinux/ | rsync | Germany | rsync subprocess killed after 15.0 seconds | 2026-05-20 12:09 | 14 | details |
| https://de.mirror.shibe.party/archlinux/ | https | Germany | Name or service not known | 2026-05-19 00:49 | 2 | details |
| http://de.mirror.shibe.party/archlinux/ | http | Germany | Name or service not known | 2026-05-19 00:49 | 2 | details |
| rsync://de.mirror.shibe.party/archlinux/ | rsync | Germany | rsync: getaddrinfo: de.mirror.shibe.party 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.2] |
2026-05-19 00:49 | 1 | details |
| rsync://fr.mirror.shibe.party/archlinux/ | rsync | France | rsync: getaddrinfo: fr.mirror.shibe.party 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.2] |
2026-05-19 00:47 | 1 | details |
| http://fr.mirror.shibe.party/archlinux/ | http | France | Name or service not known | 2026-05-19 00:47 | 1 | details |
| https://fr.mirror.shibe.party/archlinux/ | https | France | Name or service not known | 2026-05-19 00:47 | 1 | details |
| http://fr.mirror.shibe.party/archlinux/ | http | France | HTTP Error 502: Bad Gateway | 2026-05-15 11:46 | 1 | details |
| https://fr.mirror.shibe.party/archlinux/ | https | France | HTTP Error 502: Bad Gateway | 2026-05-15 11:46 | 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.