We have identified the issue and deployed a fix that seems to have mitigated the issue, but we are continuously monitoring.