We are continuing to work on a possible resolution for this incident. Our investigation has traced the trigger to a gradual rise in login traffic that has been ongoing for a few days. We are now revie

Update timeline

1. identified Aug 12, 2026, 07:06 PM UTC

   Degradation Started: performanceDegradation

2. monitoring Aug 12, 2026, 07:06 PM UTC

   We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

3. monitoring Aug 12, 2026, 07:35 PM UTC

   We’re investigating a performance degradation impacting message queue delivery for some customers. Affected customers may experience asynchronous job delays at this time. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Aug 12, 2026, 08:03 PM UTC

   Upon further investigating, we have determined that this issue is also impacting search indexes as well as some users' ability to log into their environments. We have identified the trigger and are taking action to help alleviate the impact. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Aug 12, 2026, 08:25 PM UTC

   Upon further investigation, we have determined that this issue is also impacting Global search. We are looking into additional actions to help alleviate the impact, including the possibility of increasing database capacity. We'll provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring Aug 12, 2026, 09:24 PM UTC

   We are continuing to investigate the trigger for this incident as our previous mitigation efforts have not resolved the issue as expected. We have engaged additional teams and are continuing to evaluate the possibility of increasing database capacity. We'll provide an update in 60 minutes or sooner if additional information becomes available.

7. monitoring Aug 12, 2026, 10:27 PM UTC

   We are continuing to work on a possible resolution for this incident. Our investigation has traced the trigger to a gradual rise in login traffic that has been ongoing for a few days. We are now reviewing recent account level changes that may be contributing to this pattern. Our mitigation efforts have relieved some database CPU load, but the login traffic remains high. We'll provide an update in 60 minutes or sooner if additional information becomes available.