Mirror Details: nw-sys.ru
| Name: | nw-sys.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| http://mirror.nw-sys.ru/archlinux/ | http | Russia | Yes | No | 2026-04-09 09:10 | 76.1% | 0:58 | 0.29 | 0.11 | 1.8 | Details |
| https://mirror.nw-sys.ru/archlinux/ | https | Russia | Yes | No | 2026-04-09 09:10 | 76.1% | 0:59 | 0.25 | 0.09 | 1.8 | Details |
| rsync://mirror.nw-sys.ru/archlinux/ | rsync | Russia | Yes | No | 2026-04-09 15:10 | 84.8% | 1:02 | 1.90 | 0.95 | 4.6 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| https://mirror.nw-sys.ru/archlinux/ | https | Russia | HTTP Error 502: Bad Gateway | 2026-04-09 15:48 | 6 | details |
| http://mirror.nw-sys.ru/archlinux/ | http | Russia | HTTP Error 502: Bad Gateway | 2026-04-09 15:47 | 7 | details |
| https://mirror.nw-sys.ru/archlinux/ | https | Russia | Connection timed out. | 2026-04-09 13:29 | 8 | details |
| rsync://mirror.nw-sys.ru/archlinux/ | rsync | Russia | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | 2026-04-09 13:29 | 3 | details |
| http://mirror.nw-sys.ru/archlinux/ | http | Russia | Connection timed out. | 2026-04-09 13:28 | 10 | details |
| https://mirror.nw-sys.ru/archlinux/ | https | Russia | No route to host | 2026-04-09 13:18 | 1 | details |
| http://mirror.nw-sys.ru/archlinux/ | http | Russia | No route to host | 2026-04-09 13:17 | 2 | details |
| https://mirror.nw-sys.ru/archlinux/ | https | Russia | Connection refused | 2026-04-09 11:42 | 3 | details |
| rsync://mirror.nw-sys.ru/archlinux/ | rsync | Russia | rsync: [Receiver] failed to connect to mirror.nw-sys.ru (91.122.197.74): Connection refused (111) rsync: [Receiver] failed to connect to mirror.nw-sys.ru (195.46.165.145): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-04-09 11:41 | 3 | details |
| http://mirror.nw-sys.ru/archlinux/ | http | Russia | Connection refused | 2026-04-09 11:40 | 2 | details |
| rsync://mirror.nw-sys.ru/archlinux/ | rsync | Russia | rsync: [Receiver] failed to connect to mirror.nw-sys.ru (195.46.165.145): Connection refused (111) rsync: [Receiver] failed to connect to mirror.nw-sys.ru (91.122.197.74): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-04-09 11:22 | 1 | details |
| rsync://mirror.nw-sys.ru/archlinux/ | rsync | Russia | rsync: getaddrinfo: mirror.nw-sys.ru 873: No address associated with hostname rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-04-08 16:49 | 4 | details |
| https://mirror.nw-sys.ru/archlinux/ | https | Russia | No address associated with hostname | 2026-04-08 16:48 | 4 | details |
| http://mirror.nw-sys.ru/archlinux/ | http | Russia | No address associated with hostname | 2026-04-08 16:48 | 4 | details |
| rsync://mirror.nw-sys.ru/archlinux/ | rsync | Russia | rsync: did not see server greeting rsync error: error starting client-server protocol (code 5) at main.c(1850) [Receiver=3.4.1] |
2026-04-08 15:04 | 1 | details |
| rsync://mirror.nw-sys.ru/archlinux/ | rsync | Russia | rsync subprocess killed after 15.0 seconds | 2026-04-06 08:47 | 10 | 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.