Rsync was still pointing to dev, moved the ACL back to production.
Additionally it looks like some checks are not grabbing the correct host. It always happens with the Germany check coming from 
88.198.91.70. I can't find a supporting log, but one of the errors besides the 503 indicates it checked the wrong system (an old IP possibly from a DNS server that didn't dump cache properly).
I'd like to confirm that  the check from that IP all coming from the same system before I start to dig deeper, as right now that is still the the only system reporting a problem and it seems to happen inconsistently for a single host.

The incorrect hostname it is looking at is an old DNS entry, but it is not one we are currently serving.

On Thu, Oct 18, 2018 at 1:31 PM Florian Pritz via arch-mirrors <arch-mirrors@archlinux.org> wrote:
On Thu, Oct 18, 2018 at 11:45:24AM -0500, Tails Hon1nbo <hon1nbo+mirror@hackingand.coffee> wrote:
> Please add the following to our mirror profile:
> mirror.dc02.hackingand.coffee
> Supports HTTP, HTTPS, and Rsync

Added, thank you. I seem to be getting errors with rsync though. Could
you check what's wrong? It should also be visible on our status page[1]
once the checks have run.

> > rsync rsync://mirror.dc02.hackingand.coffee/arch/
> rsync: did not see server greeting
> rsync error: error starting client-server protocol (code 5) at
> main.c(1657) [Receiver=3.1.3]

[1] https://www.archlinux.org/mirrors/hackingand.coffee/1206/

Florian

 This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.