Degraded performance of API operations due to slow database operations

The database is fully recovered, and all systems are operational. We apologize for any inconvenience this might have caused. We are currently implementing new measures to ensure this won't happen again.

All systems are operational. We expect the database to fully recover in 4 hours (1 am UTC).
We are monitoring the platform's performance. We apologize for any inconvenience this might have caused.

Actors are now fully operational, and the system is processing all the runs in time.

We are continuing to work on a fix for this issue.

We have identified the issue and are working towards recovery. The system is operational, but the capacity is capped, resulting in Actor runs being buffered in the "ready" state and a large portion of them timing out.

Our database cluster performance has further degraded, and the whole platform is facing a major outage.
We will keep informing you as the situation progresses.

We are now monitoring the situation. Worker capacity improved and is now able to handle starting Actor runs.

We are continuing to work on a fix for this issue.

Slow database operations continue to impact our systems. API performance has improved, but Actor runs are currently timing out due to reduced worker capacity.

We are currently investigating timing out operations on our API caused by slow database operations due to cluster changes.