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-05-18 19:00 |
98.9% |
12:40 |
0.52 |
0.41 |
13.7 |
Details |
https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Yes |
No |
2024-05-18 19:00 |
98.9% |
12:40 |
0.85 |
0.80 |
14.5 |
Details |
rsync://mirror.dc.uz/arch/ |
rsync |
Uzbekistan |
Yes |
No |
2024-05-18 19:00 |
98.9% |
12:40 |
2.86 |
1.90 |
17.6 |
Details |
Error Log
Mirror URL |
Protocol |
Country |
Error Message |
Last Occurred |
Occurrences (last 168 hours) |
|
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-05-18 19:09 |
1 |
details |
https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Connection timed out. |
2024-05-18 19:09 |
3 |
details |
http://mirror.dc.uz/arch/ |
http |
Uzbekistan |
Connection timed out. |
2024-05-18 19:09 |
1 |
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.3.0] |
2024-05-17 00:33 |
1 |
details |
https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Name or service not known |
2024-05-17 00:33 |
1 |
details |
http://mirror.dc.uz/arch/ |
http |
Uzbekistan |
Name or service not known |
2024-05-17 00:33 |
1 |
details |
https://mirror.dc.uz/arch/ |
https |
Uzbekistan |
Exception in processing HTTP request. |
2024-05-16 15:41 |
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.