Previous incidents

March 14, 2022, 14:15（UTC）
The inaccessible issue is resolved now.

2022年3月14日23:15（JST）
スペースへ入室できない障害について、復旧いたしました。

February 28, 2022, 7:30（UTC）
We have completed the correction process as scheduled.
2022年3月1日5:00（JST）
予定通り修正作業を完了しました。

Why this happened

We switched to a new server cluster during the Echo server maintenance conducted on February 20. We had prepared the servers based on the past load, but the load balancer that distributes requests to the servers could not withstand the load and could not accept some requests.
In this recovery work, we reverted to the old cluster.

How to prevent this in the future

We will enhance the load balancer's performance so that it can withstand the expected number of reque...

Maintenance has been successfully completed.
February 20, 16:00 (UTC) - February 20, 17:00 (UTC)

As a result of automatically increasing or decreasing the number of servers depending on the load, there were cases where reboots were triggered under certain conditions. When this happened, meetings were disconnected or people were forced to leave the space.
We have fixed the problem so that the reboot process will not run under certain conditions.
We apologize for the inconvenience caused over a long period of time.
負荷に応じて自動でサーバーの数を増減するように対応した結果、特定の条件下で再起動がかかってしまうケースがあり、そのときに会議が切断したり、スペー...

14:00 問題が解消しました。

The issue was resolved at 14:00.