The problem has been identified and fixed, we've deployed a new version and we're back online. Root cause: our database migration script executed commands in the wrong order, causing errored migration in rare scenarios. We've finally hit one of these scenarios and faced the music.

We tried to release a new version to dev, resulting in the application going down. We're investigating.