We have determined that this issue is related to resource capacity constraints on the underlying database infrastructure. To mitigate the issue we have restarted the affected database nodes. We're clo

Update timeline

1. identified Jun 03, 2026, 03:13 AM UTC

   Degradation Started: performanceDegradation

2. monitoring Jun 03, 2026, 05:38 AM UTC

   We are investigating a performance degradation where a subset of users may experience slow console performance. We have identified the cause and are actively working to restore full service. We're currently restarting backend services on the affected instances to resolve the issue. Please note that the scope of impact has expanded, and we're monitoring additional instances showing similar symptoms. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 03, 2026, 06:00 AM UTC

   Work continues on restarting backend services on the affected instances. In parallel we are also assessing potential impacts on other instances, as well as further remediation actions. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jun 03, 2026, 06:19 AM UTC

   Investigation and restoration efforts remain ongoing. We'll provide an update in 30 minutes or sooner if additional information becomes available, and apologize for any inconvenience this is causing.

5. monitoring Jun 03, 2026, 06:48 AM UTC

   We have determined that this issue is related to resource capacity constraints on the underlying database infrastructure. To mitigate the issue we have restarted the affected database nodes. We're closely monitoring the system's performance following these restarts to evaluate their effectiveness in restoring optimal service levels. We'll provide another update in 30 minutes, or sooner if additional information becomes available.