Affected
We implemented a fix and are currently seeing recovery.
A postmortem of this incident can be found here.
We have identified the issue and are currently rolling back the change.