Mirror Details: rackspace.com
| Name: | rackspace.com |
|---|---|
| Tier: | Tier 1 |
| Has ISOs: | Yes |
Available URLs
| Mirror URL | Protocol | Country | IPv4 | IPv6 | Last Sync | Completion % | μ Delay (hh:mm) | μ Duration (s) | σ Duration (s) | Score | Details |
|---|---|---|---|---|---|---|---|---|---|---|---|
| http://dfw.mirror.rackspace.com/archlinux/ | http | United States | Yes | No | 2026-02-14 18:30 | 100.0% | 5:06 | 0.49 | 0.19 | 5.8 | Details |
| http://hkg.mirror.rackspace.com/archlinux/ | http | Hong Kong | Yes | No | 2026-02-14 18:30 | 100.0% | 5:11 | 0.73 | 0.30 | 6.2 | Details |
| http://iad.mirror.rackspace.com/archlinux/ | http | United States | Yes | No | 2026-02-14 18:30 | 100.0% | 5:15 | 0.31 | 0.14 | 5.7 | Details |
| http://lon.mirror.rackspace.com/archlinux/ | http | United Kingdom | Yes | No | 2026-02-14 18:30 | 100.0% | 5:20 | 0.14 | 0.12 | 5.6 | Details |
| http://mirror.rackspace.com/archlinux/ | http | Yes | No | 2026-02-14 18:30 | 100.0% | 5:20 | 0.26 | 0.14 | 5.7 | Details | |
| http://ord.mirror.rackspace.com/archlinux/ | http | United States | Yes | No | 2026-02-14 22:30 | 100.0% | 2:18 | 0.46 | 0.16 | 2.9 | Details |
| http://syd.mirror.rackspace.com/archlinux/ | http | Australia | Yes | No | 2026-02-14 18:30 | 100.0% | 5:35 | 0.73 | 0.13 | 6.4 | Details |
| https://dfw.mirror.rackspace.com/archlinux/ | https | United States | Yes | No | 2026-02-14 18:30 | 100.0% | 5:06 | 0.40 | 0.09 | 5.6 | Details |
| https://hkg.mirror.rackspace.com/archlinux/ | https | Hong Kong | Yes | No | 2026-02-14 18:30 | 100.0% | 5:11 | 0.79 | 0.31 | 6.3 | Details |
| https://iad.mirror.rackspace.com/archlinux/ | https | United States | Yes | No | 2026-02-14 18:30 | 100.0% | 5:15 | 0.32 | 0.08 | 5.7 | Details |
| https://lon.mirror.rackspace.com/archlinux/ | https | United Kingdom | Yes | No | 2026-02-14 18:30 | 100.0% | 5:20 | 0.08 | 0.06 | 5.5 | Details |
| https://mirror.rackspace.com/archlinux/ | https | Yes | No | 2026-02-14 18:30 | 100.0% | 5:20 | 0.12 | 0.11 | 5.6 | Details | |
| https://ord.mirror.rackspace.com/archlinux/ | https | United States | Yes | No | 2026-02-14 22:30 | 100.0% | 2:18 | 0.35 | 0.10 | 2.8 | Details |
| https://syd.mirror.rackspace.com/archlinux/ | https | Australia | Yes | No | 2026-02-14 18:30 | 100.0% | 5:35 | 0.80 | 0.02 | 6.4 | Details |
| rsync://dfw.mirror.rackspace.com/archlinux/ | rsync | United States | Yes | No | unknown | unknown | 0.26 | 0.15 | ∞ | Details | |
| rsync://hkg.mirror.rackspace.com/archlinux/ | rsync | Hong Kong | Yes | No | unknown | unknown | 0.39 | 0.20 | ∞ | Details | |
| rsync://iad.mirror.rackspace.com/archlinux/ | rsync | United States | Yes | No | unknown | unknown | 0.33 | 0.18 | ∞ | Details | |
| rsync://lon.mirror.rackspace.com/archlinux/ | rsync | United Kingdom | Yes | No | unknown | unknown | 0.19 | 0.13 | ∞ | Details | |
| rsync://mirror.rackspace.com/archlinux/ | rsync | Yes | No | unknown | unknown | 0.15 | 0.14 | ∞ | Details | ||
| rsync://ord.mirror.rackspace.com/archlinux/ | rsync | United States | Yes | No | unknown | unknown | 0.30 | 0.14 | ∞ | Details | |
| rsync://syd.mirror.rackspace.com/archlinux/ | rsync | Australia | Yes | No | unknown | unknown | 0.42 | 0.13 | ∞ | Details |
Error Log
| Mirror URL | Protocol | Country | Error Message | Last Occurred | Occurrences (last 168 hours) | |
|---|---|---|---|---|---|---|
| rsync://lon.mirror.rackspace.com/archlinux/ | rsync | United Kingdom | rsync: [Receiver] failed to connect to lon.mirror.rackspace.com (94.236.26.35): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-02-15 01:03 | 276 | details |
| rsync://hkg.mirror.rackspace.com/archlinux/ | rsync | Hong Kong | rsync: [Receiver] failed to connect to hkg.mirror.rackspace.com (180.150.156.88): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-02-15 01:03 | 299 | details |
| rsync://syd.mirror.rackspace.com/archlinux/ | rsync | Australia | rsync: [Receiver] failed to connect to syd.mirror.rackspace.com (119.9.32.73): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-02-15 01:03 | 297 | details |
| rsync://ord.mirror.rackspace.com/archlinux/ | rsync | United States | rsync: [Receiver] failed to connect to ord.mirror.rackspace.com (166.78.229.131): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-02-15 01:03 | 294 | details |
| rsync://dfw.mirror.rackspace.com/archlinux/ | rsync | United States | rsync: [Receiver] failed to connect to dfw.mirror.rackspace.com (74.205.112.120): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-02-15 01:03 | 295 | details |
| rsync://iad.mirror.rackspace.com/archlinux/ | rsync | United States | rsync: [Receiver] failed to connect to iad.mirror.rackspace.com (72.4.120.219): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-02-15 01:03 | 295 | details |
| rsync://mirror.rackspace.com/archlinux/ | rsync | rsync: [Receiver] failed to connect to mirror.rackspace.com (94.236.26.35): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-02-15 01:03 | 295 | details | |
| rsync://lon.mirror.rackspace.com/archlinux/ | rsync | United Kingdom | rsync: [Receiver] failed to connect to lon.mirror.rackspace.com (94.236.26.35): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
2026-02-14 14:27 | 19 | details |
| https://iad.mirror.rackspace.com/archlinux/ | https | United States | Connection refused | 2026-02-11 13:00 | 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.