Mirror Details: accuris.ca
Name: | accuris.ca |
---|---|
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.accuris.ca/archlinux/ | http | Canada | Yes | Yes | unknown | unknown | ∞ | Details | |||
https://mirror.accuris.ca/archlinux/ | https | Canada | Yes | Yes | unknown | unknown | ∞ | Details | |||
rsync://mirror.accuris.ca/archlinux/ | rsync | Canada | Yes | Yes | unknown | unknown | 2.84 | 1.42 | ∞ | Details |
Error Log
Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
---|---|---|---|---|---|---|
rsync://mirror.accuris.ca/archlinux/ | rsync | Canada | rsync: [Receiver] failed to connect to mirror.accuris.ca (2602:fcd3:1::5): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-11-10 18:58 | 543 | details |
http://mirror.accuris.ca/archlinux/ | http | Canada | No route to host | 2024-11-10 18:58 | 1216 | details |
https://mirror.accuris.ca/archlinux/ | https | Canada | No route to host | 2024-11-10 18:58 | 1211 | details |
rsync://mirror.accuris.ca/archlinux/ | rsync | Canada | rsync: [Receiver] failed to connect to mirror.accuris.ca (23.130.139.5): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-11-10 18:56 | 674 | details |
rsync://mirror.accuris.ca/archlinux/ | rsync | Canada | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] | 2024-11-10 03:33 | 18 | details |
http://mirror.accuris.ca/archlinux/ | http | Canada | Connection timed out. | 2024-11-10 03:33 | 19 | details |
https://mirror.accuris.ca/archlinux/ | https | Canada | Connection timed out. | 2024-11-10 03:33 | 24 | 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.