Mirror Details: udenar.edu.co
| Name: | udenar.edu.co |
|---|---|
| Tier: | Tier 2 |
| Has ISOs: | Yes |
Available URLs
| Mirror URL | Protocol | Country | IPv4 | IPv6 | Last Sync | Completion % | μ Delay (hh:mm) | μ Duration (s) | σ Duration (s) | Score | Details |
|---|---|---|---|---|---|---|---|---|---|---|---|
| http://mirrors.udenar.edu.co/archlinux/ | http | Colombia | Yes | No | 2026-08-25 22:01 | 100.0% | 0:34 | 0.86 | 1.24 | 2.7 | Details |
| rsync://mirrors.udenar.edu.co/archlinux/ | rsync | Colombia | Yes | No | 2026-08-25 22:01 | 100.0% | 0:34 | 3.14 | 1.52 | 5.2 | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| http://mirrors.udenar.edu.co/archlinux/ | http | Colombia | Connection timed out. | 2026-08-24 20:38 | 4 | details |
| rsync://mirrors.udenar.edu.co/archlinux/ | rsync | Colombia | rsync error: timeout waiting for daemon connection (code 35) at socket.c(429) [Receiver=3.5.0-g471e17dc] | 2026-08-22 21:09 | 2 | details |
| rsync://mirrors.udenar.edu.co/archlinux/ | rsync | Colombia | rsync: getaddrinfo: mirrors.udenar.edu.co 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(165) [Receiver=3.5.0-g471e17dc] |
2026-08-22 20:40 | 1 | details |
| http://mirrors.udenar.edu.co/archlinux/ | http | Colombia | Name or service not known | 2026-08-22 20:40 | 2 | details |
| rsync://mirrors.udenar.edu.co/archlinux/ | rsync | Colombia | rsync subprocess killed after 15.0 seconds | 2026-08-22 20:12 | 2 | details |
| rsync://mirrors.udenar.edu.co/archlinux/ | rsync | Colombia | rsync: [Receiver] failed to connect to mirrors.udenar.edu.co (192.68.185.32): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(165) [Receiver=3.5.0-g471e17dc] |
2026-08-19 21:03 | 1 | details |
| http://mirrors.udenar.edu.co/archlinux/ | http | Colombia | No route to host | 2026-08-19 21:03 | 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.