Mirror Details: dc.uz
| Name: | dc.uz |
|---|---|
| Tier: | Tier 2 |
| Has ISOs: | No |
Available URLs
| Mirror URL | Protocol | Country | IPv4 | IPv6 | Last Sync | Completion % | μ Delay (hh:mm) | μ Duration (s) | σ Duration (s) | Score | Details |
|---|---|---|---|---|---|---|---|---|---|---|---|
| http://mirror.dc.uz/arch/ | http | Uzbekistan | Yes | No | 2025-02-20 19:02 | 94.7% | 12:53 | 0.79 | 1.27 | 15.8 | Details |
| https://mirror.dc.uz/arch/ | https | Uzbekistan | Yes | No | 2025-02-20 19:02 | 94.7% | 12:39 | 1.18 | 1.61 | 16.3 | Details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | Yes | No | 2025-02-20 19:02 | 98.7% | 12:29 | 3.43 | 2.56 | 18.7 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| https://mirror.dc.uz/arch/ | https | Uzbekistan | Connection timed out. | 2025-02-21 15:18 | 31 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | [Receiver] io timeout after 10 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-20 22:44 | 15 | details |
| http://mirror.dc.uz/arch/ | http | Uzbekistan | Connection timed out. | 2025-02-20 22:44 | 21 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | [Receiver] io timeout after 12 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-18 20:47 | 2 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | 2025-02-17 23:25 | 2 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | [Receiver] io timeout after 11 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-16 12:54 | 3 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | rsync: getaddrinfo: mirror.dc.uz 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2025-02-16 10:28 | 3 | details |
| https://mirror.dc.uz/arch/ | https | Uzbekistan | Name or service not known | 2025-02-16 10:28 | 3 | details |
| http://mirror.dc.uz/arch/ | http | Uzbekistan | Name or service not known | 2025-02-16 10:28 | 3 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | [Receiver] io timeout after 18 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-15 08:10 | 1 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | [Receiver] io timeout after 15 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-15 05:15 | 1 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | [Receiver] io timeout after 16 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-02-15 02:02 | 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.