This incident has been resolved.

We have managed to stabilize the API, will be monitoring to ensure this persists. Thanks for your patience!

We are still investigating the root cause of the issue