The problem was due to some memory corruption issues on the server caused by some C extensions. We tracked down the issue and shipped a fix. We’ll continue monitoring the situation.

We’re receiving feedback of slow responses and intermittent 503 error codes on our Content Management API, we’ve doubled up our server resources and investigating in the meantime