Earlier today, we experienced a spike in memory usage on our database, which in turn caused a temporary increase in CPU load. This placed some strain on our systems, including the API and background processes. We’ve now mitigated the issue and system performance has returned to normal.

We’re still investigating the trigger behind the memory spike, and we’re actively working on measures to reduce the risk of this happening again.

We are currently experiencing slowdown across the entire system, affecting all customers. This is top priority for us, and we are investigating urgently.