Please share your location; we will try to replicate your issue with a VPN from your area.
We are also seeing timeouts again (Australia)
I contacted my colleagues from the admin team, and they told me there was an issue with the VM when it responded to the health check but failed to respond to other requests. We redeployed these VMs and will look more closely at what is happening to them. Please check that you don’t get timeouts now.
@yaroslaw.ekimov
Yesterday it was ok, but now it is back again.
meaning not working again.
same errors
We are sorry this issue still exists. We are analyzing it and cannot predict why and when it may happen. As a workaround, our VMs will be restarted two times a day so that it won’t affect users with this error. The VMs were restarted this morning, so now you shouldn’t get timeout errors.
We are working hard to eliminate this issue ASAP.
We are tweaking our servers and all infrastructure middleware to be stable, but the issue remains unresolved and we work hard to fix it ASAP.
The issue with timeouts is already a high priority.
Thanks for your patience.
The issues you have found earlier (filed as WORDSCLOUD-2721) have been fixed in this update. This message was posted using Bugs notification tool by Ivanov_John