Service API seems to be down
Root cause was identified to be a dependency that removed support for Python 2 that was used to orchestrate the deployment pipeline. Through that change, automatic scaling and deployment of API instances could no longer be performed, which led to the API instance CPU load to max out. The deployment pipeline has been updated accordingly.
Instances recovered through the rollback and are back up as of 18:02 CET. We are investigating the root cause.
Service is back up.
We are attempting a rollback of a Postgres connection scaling change that was deployed earlier today.
We are investigating the issue.
According to our monitoring system this service has become unresponsive, we’re investigating.