Mirror Details: sl-chat.ru
| Name: | sl-chat.ru |
|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://mirror1.sl-chat.ru/archlinux/ | https | Finland | Yes | No | 2024-12-25 16:00 | 93.5% | 0:40 | 0.39 | 0.30 | 1.5 | Details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | Yes | No | 2024-12-25 16:00 | 93.5% | 0:40 | 0.36 | 0.25 | 1.4 | Details |
| https://mirror3.sl-chat.ru/archlinux/ | https | Russia | Yes | No | 2024-12-25 15:13 | 98.9% | 0:59 | 0.49 | 0.36 | 1.9 | Details |
| rsync://mirror1.sl-chat.ru/archlinux/ | rsync | Finland | Yes | No | 2024-12-25 16:00 | 93.5% | 0:41 | 1.28 | 0.88 | 3.0 | Details |
| rsync://mirror2.sl-chat.ru/archlinux/ | rsync | Russia | Yes | No | 2024-12-25 16:00 | 93.5% | 0:41 | 1.31 | 0.90 | 3.1 | Details |
| rsync://mirror3.sl-chat.ru/archlinux/ | rsync | Russia | Yes | No | 2024-12-25 15:13 | 98.9% | 0:59 | 1.73 | 0.85 | 3.6 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| rsync://mirror3.sl-chat.ru/archlinux/ | rsync | Russia | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] | 2024-12-25 08:38 | 5 | details |
| https://mirror3.sl-chat.ru/archlinux/ | https | Russia | Connection timed out. | 2024-12-25 08:38 | 15 | details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | Connection refused | 2024-12-24 19:58 | 3 | details |
| https://mirror1.sl-chat.ru/archlinux/ | https | Finland | Connection refused | 2024-12-24 19:58 | 3 | details |
| rsync://mirror2.sl-chat.ru/archlinux/ | rsync | Russia | rsync: [Receiver] failed to connect to mirror2.sl-chat.ru (92.101.122.43): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-12-24 19:50 | 8 | details |
| rsync://mirror1.sl-chat.ru/archlinux/ | rsync | Finland | rsync: [Receiver] failed to connect to mirror1.sl-chat.ru (92.101.122.43): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-12-24 19:50 | 8 | details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | No route to host | 2024-12-24 19:50 | 8 | details |
| https://mirror1.sl-chat.ru/archlinux/ | https | Finland | No route to host | 2024-12-24 19:50 | 8 | details |
| rsync://mirror2.sl-chat.ru/archlinux/ | rsync | Russia | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] | 2024-12-24 19:11 | 245 | details |
| rsync://mirror1.sl-chat.ru/archlinux/ | rsync | Finland | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] | 2024-12-24 19:11 | 245 | details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | Connection timed out. | 2024-12-24 19:10 | 9 | details |
| https://mirror1.sl-chat.ru/archlinux/ | https | Finland | Connection timed out. | 2024-12-24 19:10 | 9 | details |
| rsync://mirror2.sl-chat.ru/archlinux/ | rsync | Russia | rsync: [Receiver] failed to connect to mirror2.sl-chat.ru (92.101.122.43): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-12-24 18:53 | 1 | details |
| rsync://mirror1.sl-chat.ru/archlinux/ | rsync | Finland | rsync: [Receiver] failed to connect to mirror1.sl-chat.ru (92.101.122.43): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-12-24 18:53 | 1 | details |
| rsync://mirror3.sl-chat.ru/archlinux/ | rsync | Russia | rsync: [Receiver] failed to connect to mirror3.sl-chat.ru (91.210.150.214): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0] |
2024-12-21 03:30 | 1 | details |
| https://mirror3.sl-chat.ru/archlinux/ | https | Russia | Connection refused | 2024-12-21 03:30 | 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.