I noticed this issue too but it resolved by now. Has it resolved for you as well? Still, the question remains how that can happen, how to handle it on the dev side (if possible) and how reliably the status codes are.