I tried to access my cloud instance this morning but I received a 503 error instead.
I remembered there was a similar bug last year, so I dealt with it as I did then — by changing the desired location of the instance.
That got the service up and running again, but this is a serious bug that needs fixing.
Now I'm wondering whether this was the reason the stable version v21.2 was pulled from the downloads page.
Customer support service by UserEcho