Previous incidents

API recovered automatically after AWS triggered a server shutdown.

This is caused by our production environment currently being configured with just a single instance running of the back-end. In the future, we'll have multiple instances running, so that a restart of a single instance does not cause downtime.

The API is up, after an automatic recovery by our internal monitoring.

To mitigate errors like this in the future, the server cluster in AWS will get full health checks added, and we'll disable Service Connect as it has caused similar issues before.