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 |
2026-08-26 20:01 |
89.1% |
12:25 |
0.50 |
0.31 |
14.9 |
Details |
| https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Yes |
No |
2026-08-26 20:01 |
89.1% |
12:25 |
0.84 |
0.58 |
15.5 |
Details |
| rsync://mirror.dc.uz/arch/ |
rsync |
Uzbekistan |
Yes |
No |
2026-08-26 20:01 |
93.5% |
12:00 |
3.15 |
2.30 |
18.7 |
Details |
Error Log
| Mirror URL |
Protocol |
Country |
Error Message |
Last Occurred |
Occurrences (last 168 hours) |
|
| rsync://mirror.dc.uz/arch/ |
rsync |
Uzbekistan |
rsync subprocess killed after 15.0 seconds |
2026-08-27 02:14 |
8 |
details |
| https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Connection timed out. |
2026-08-27 02:14 |
16 |
details |
| http://mirror.dc.uz/arch/ |
http |
Uzbekistan |
Connection timed out. |
2026-08-27 02:14 |
16 |
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(248) [Receiver=3.5.0-g471e17dc] |
2026-08-26 23:25 |
1 |
details |
| http://mirror.dc.uz/arch/ |
http |
Uzbekistan |
[Errno 104] Connection reset by peer |
2026-08-23 00:21 |
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.