Performance Degradation

After reviewing additional error logs, we decided to update the Trust status page for the CS110 instance individually to capture the most accurate duration of impact, as we noted that the start time and end times of the impact need to be revised. We apologize for any confusion this may have caused.

At 12:45 UTC, the Salesforce Technology team implemented a fix to resolve the exceptions at the database tier that brought the customers out of impact on the CS24 instance. The team is currently monitoring the performance levels. Initial reports are indicating positive outcomes. In parallel, the team is also implementing the fix on the CS110 instance. We are confident that the fix will provide desired outcomes on the CS110 instance.

We will provide an update in 30 minutes or sooner if we have more information.

After initial investigations, the team noted some exceptions at the database tier to be the potential trigger for the issue. However, this is being validated further. The team is also exploring other paths in resolving the issue. During the course of investigation, we noted that CS110 is also impacted as a result of this incident and hence we decided to add it to the Trust status page. We may continue to update the Trust status page as we get the additional instances that may be impacted due to this issue.

We will provide an update in 30 minutes or sooner if we have more information.

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

The Salesforce Technology team is aware of an issue that has resulted in a reported performance degradation for a subset of customers on CS24 sandbox instance. Users are able to access the service, however, some functionality within the service may not be available or running at optimal performance. During this time a subset of customers may experience issues while deploying changes and may also experience internal server errors when attempting to create new records. The team is investigating the issue and is currently working to identify the full scope and impact of the issue.

We will provide an update in 30 minutes, or sooner as additional information becomes available.