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-17 19:01 100.0% 14:18 0.47 0.22 15.0 Details
https://mirror.dc.uz/arch/ https Uzbekistan Yes No 2026-08-17 19:01 100.0% 14:18 0.67 0.34 15.3 Details
rsync://mirror.dc.uz/arch/ rsync Uzbekistan Yes No 2026-08-17 19:01 100.0% 14:18 2.52 0.99 17.8 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-16 17:26 8 details
http://mirror.dc.uz/arch/ http Uzbekistan [Errno 104] Connection reset by peer 2026-08-15 22:01 4 details
rsync://mirror.dc.uz/arch/ rsync Uzbekistan rsync: [Receiver] safe_read failed to read 1 bytes: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(283) [Receiver=3.4.4]
2026-08-15 21:21 1 details
https://mirror.dc.uz/arch/ https Uzbekistan Connection timed out. 2026-08-15 21:15 11 details
http://mirror.dc.uz/arch/ http Uzbekistan Connection timed out. 2026-08-15 21:15 11 details
rsync://mirror.dc.uz/arch/ rsync Uzbekistan rsync error: timeout waiting for daemon connection (code 35) at socket.c(282) [Receiver=3.4.4] 2026-08-15 04:35 1 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.4]
2026-08-15 00:27 1 details
https://mirror.dc.uz/arch/ https Uzbekistan Connection reset by peer 2026-08-14 17:20 2 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.