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 |
2024-04-28 19:00 |
100.0% |
12:48 |
0.50 |
0.33 |
13.6 |
Details |
| https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Yes |
No |
2024-04-28 19:00 |
100.0% |
12:48 |
0.78 |
0.58 |
14.2 |
Details |
| rsync://mirror.dc.uz/arch/ |
rsync |
Uzbekistan |
Yes |
No |
2024-04-28 19:00 |
100.0% |
12:48 |
2.83 |
1.68 |
17.3 |
Details |
Error Log
| Mirror URL |
Protocol |
Country |
Error Message |
Last Occurred |
Occurrences (last 168 hours) |
|
| 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.3.0] |
2024-04-27 16:22 |
1 |
details |
| https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Name or service not known |
2024-04-27 16:22 |
1 |
details |
| http://mirror.dc.uz/arch/ |
http |
Uzbekistan |
Name or service not known |
2024-04-27 16:22 |
1 |
details |
| rsync://mirror.dc.uz/arch/ |
rsync |
Uzbekistan |
rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] |
2024-04-26 17:22 |
4 |
details |
| https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Connection timed out. |
2024-04-26 17:22 |
4 |
details |
| http://mirror.dc.uz/arch/ |
http |
Uzbekistan |
Connection timed out. |
2024-04-26 17:22 |
4 |
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.