RESURFACED: Intermittent Timeouts Observed on US Production Environment

Update timeline

1. investigating Jun 02, 2026, 02:35 PM UTC

   CSOD Engineering teams have detected spikes in intermittent timeouts on the backend, indicating that the issue reported yesterday (01 June 2026) has resurfaced. As a result, some customers on the US swimlanes (SL1, SL2, SL3, and SL5) may witness intermittent timeouts while accessing or navigating the application. Our Engineering teams are actively investigating the issue and working to restore stability. We will provide another update as soon as additional information becomes available.

2. identified Jun 02, 2026, 05:51 PM UTC

   We are planning Emergency Maintenance today at 9:00 PM PT to address this issue. During the maintenance window, the system may be unavailable for up to one hour. Intermittent timeouts may continue until the maintenance is completed. The maintenance is being scheduled outside of peak business hours to reduce overall customer impact. We will continue to provide additional updates as more information becomes available.

3. resolved Jun 03, 2026, 05:20 AM UTC

   The scheduled Emergency maintenance has been completed, and the intermittent timeout issues should be resolved now.

4. postmortem Jun 23, 2026, 08:13 AM UTC

   **Incident Summary:** On June 2nd, 2026, clients in the US Production environment \(SL1, SL2, SL3, and SL5\) experienced brief latency. The issue primarily impacted platform responsiveness, request processing, and caused timeout errors. **Impact:** Users experienced intermittent latency and delayed responses while accessing services. The degradation affected multiple application flows, leading to slower response times during the incident window. **Root Cause Analysis \(RCA\):** The issue was related to insufficient service capacity during a period of increased demand. As traffic levels increased, request processing delays were observed, resulting in intermittent latency and degraded responsiveness across affected services. **Resolution:** As an immediate mitigation, service capacity was increased in the impacted environment to better handle runtime load conditions. This action stabilized request processing and restored normal service performance. **Preventive Actions:** The following measures have been implemented to reduce the likelihood of recurrence: * Baseline capacity has been adjusted to better support expected traffic patterns