This should be fixed now after a quick deployment this afternoon