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-03-13 19:02 | 92.4% | 12:31 | 0.93 | 1.53 | 16.2 | Details |
| https://mirror.dc.uz/arch/ | https | Uzbekistan | Yes | No | 2025-03-13 19:02 | 92.4% | 12:31 | 1.15 | 1.43 | 16.3 | Details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | Yes | No | 2025-03-13 19:02 | 96.2% | 12:14 | 5.29 | 15.10 | 33.9 | 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-03-14 05:13 | 36 | details |
| http://mirror.dc.uz/arch/ | http | Uzbekistan | Connection timed out. | 2025-03-14 05:13 | 35 | 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-03-14 01:56 | 14 | 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-03-12 00:27 | 2 | 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.