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-04-28 19:01 100.0% 12:47 0.41 0.18 13.4 Details
https://mirror.dc.uz/arch/ https Uzbekistan Yes No 2026-04-28 19:01 100.0% 12:47 0.59 0.27 13.6 Details
rsync://mirror.dc.uz/arch/ rsync Uzbekistan Yes No 2026-04-28 19:01 100.0% 12:47 2.30 0.89 16.0 Details

Error Log

Mirror URL Protocol Country Error Message Last Occurred Occurrences (last 168 hours)
rsync://mirror.dc.uz/arch/ rsync Uzbekistan rsync: [Receiver] failed to connect to mirror.dc.uz (91.212.89.107): No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1]		 2026-04-27 10:09 4 details
https://mirror.dc.uz/arch/ https Uzbekistan HTTP Error 502: Bad Gateway 2026-04-27 10:09 4 details
http://mirror.dc.uz/arch/ http Uzbekistan HTTP Error 502: Bad Gateway 2026-04-27 10:09 4 details
rsync://mirror.dc.uz/arch/ rsync Uzbekistan rsync subprocess killed after 15.0 seconds 2026-04-26 21:53 2 details
https://mirror.dc.uz/arch/ https Uzbekistan Connection timed out. 2026-04-26 21:53 5 details
http://mirror.dc.uz/arch/ http Uzbekistan Connection timed out. 2026-04-26 21:53 5 details
http://mirror.dc.uz/arch/ http Uzbekistan [Errno 104] Connection reset by peer 2026-04-26 21:43 1 details
rsync://mirror.dc.uz/arch/ rsync Uzbekistan rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] 2026-04-23 04:48 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.