This issue was caused by invalid configuration on our status page. No actual service degradation occured.