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-19 19:01 | 81.5% | 14:24 | 0.97 | 1.37 | 20.6 | Details |
| https://mirror.dc.uz/arch/ | https | Uzbekistan | Yes | No | 2025-03-19 19:01 | 80.2% | 14:35 | 1.17 | 1.24 | 21.2 | Details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | Yes | No | 2025-03-19 19:01 | 90.1% | 13:32 | 8.26 | 27.74 | 55.0 | 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-20 06:39 | 42 | details |
| http://mirror.dc.uz/arch/ | http | Uzbekistan | Connection timed out. | 2025-03-20 06:39 | 41 | 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-20 05:44 | 15 | details |
| rsync://mirror.dc.uz/arch/ | rsync | Uzbekistan | [Receiver] io timeout after 14 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(201) [Receiver=3.4.1] |
2025-03-14 22:40 | 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.