Mirror Details: wearetriple.com
Name: | wearetriple.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://archlinux.mirror.wearetriple.com/ | http | Netherlands | Yes | Yes | 2024-05-17 16:00 | 90.9% | 1:15 | 0.27 | 0.46 | 2.2 | Details |
https://archlinux.mirror.wearetriple.com/ | https | Netherlands | Yes | Yes | 2024-05-17 16:00 | 90.9% | 1:15 | 0.49 | 0.77 | 2.8 | Details |
rsync://mirror.wearetriple.com/archlinux/ | rsync | Netherlands | Yes | Yes | unknown | unknown | 0.15 | 0.20 | ∞ | Details |
Error Log
Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
---|---|---|---|---|---|---|
rsync://mirror.wearetriple.com/archlinux/ | rsync | Netherlands | rsync: [Receiver] failed to connect to mirror.wearetriple.com (2a00:1f00:dc06:10::106): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-05-17 18:08 | 675 | details |
rsync://mirror.wearetriple.com/archlinux/ | rsync | Netherlands | rsync: [Receiver] failed to connect to mirror.wearetriple.com (93.187.10.106): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-05-17 18:05 | 675 | details |
https://archlinux.mirror.wearetriple.com/ | https | Netherlands | Could not parse time from lastsync | 2024-05-17 02:09 | 17 | details |
http://archlinux.mirror.wearetriple.com/ | http | Netherlands | Could not parse time from lastsync | 2024-05-17 02:09 | 17 | details |
https://archlinux.mirror.wearetriple.com/ | https | Netherlands | Connection timed out. | 2024-05-13 07:22 | 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.