We have identified the cause: a code error generated an incorrect response, which BetterStack interpreted as a 503 redirect. The issue has been fixed, and we have also updated the BetterStack configuration to prevent similar errors in the future.