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 | 2025-01-13 18:16 | 10.9% | 0:45 | 0.54 | 0.45 | 16.0 | Details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | Yes | No | 2025-01-13 18:16 | 10.9% | 0:45 | 0.49 | 0.38 | 14.8 | Details |
| https://mirror3.sl-chat.ru/archlinux/ | https | Russia | Yes | No | 2025-01-13 18:14 | 100.0% | 1:06 | 0.57 | 0.43 | 2.1 | Details |
| rsync://mirror1.sl-chat.ru/archlinux/ | rsync | Finland | Yes | No | unknown | unknown | 0.62 | 0.90 | ∞ | Details | |
| rsync://mirror2.sl-chat.ru/archlinux/ | rsync | Russia | Yes | No | unknown | unknown | 0.57 | 0.82 | ∞ | Details | |
| rsync://mirror3.sl-chat.ru/archlinux/ | rsync | Russia | Yes | No | 2025-01-13 18:14 | 100.0% | 1:06 | 2.00 | 1.02 | 4.1 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| 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] | 2025-01-13 18:54 | 518 | 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] | 2025-01-13 18:54 | 518 | details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | Connection refused | 2025-01-13 15:56 | 9 | details |
| https://mirror1.sl-chat.ru/archlinux/ | https | Finland | Connection refused | 2025-01-13 15:56 | 9 | details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | HTTP Error 404: Not Found | 2025-01-13 15:39 | 38 | details |
| https://mirror1.sl-chat.ru/archlinux/ | https | Finland | HTTP Error 404: Not Found | 2025-01-13 15:39 | 38 | 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] |
2025-01-13 11:46 | 7 | 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] |
2025-01-13 11:46 | 7 | details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | Connection timed out. | 2025-01-13 01:08 | 9 | details |
| https://mirror1.sl-chat.ru/archlinux/ | https | Finland | Connection timed out. | 2025-01-13 01:08 | 9 | 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] |
2025-01-12 21:55 | 2 | 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] |
2025-01-12 21:55 | 2 | details |
| https://mirror2.sl-chat.ru/archlinux/ | https | Russia | HTTP Error 500: Internal Server Error | 2025-01-12 19:34 | 3 | details |
| https://mirror1.sl-chat.ru/archlinux/ | https | Finland | HTTP Error 500: Internal Server Error | 2025-01-12 19:34 | 3 | details |
| 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] | 2025-01-11 20:43 | 3 | details |
| https://mirror3.sl-chat.ru/archlinux/ | https | Russia | Connection timed out. | 2025-01-11 20:43 | 3 | 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.