The issue is resolved. It was due to an error caused by our DB provider when performing a standard DB operation. We are contacting them to ensure this never happens again, and apologize for any inconvenience caused.

Our API was down due to a failure with our DB provider. We are working urgently to fix this and will provide an update shortly