It’s back to live again, however I got goosebumps for a moment. If this is a side effect of deployment/stack switch/infrastructure downtime, there probably should be some other error message or a 503 page.
This is known issue, we are looking into it. Thanks!
This bug is fixed.