Companies / Salesforce / incidents

Salesforce: Performance Degradation: Core Service

Affected components: Core Service13 instances

Timeline of updates

1. update2026-01-07 12:47 UTC

   Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

2. update2026-01-07 13:03 UTC

   We are addressing an issue impacting multiple instances. New application servers cannot start due to a missing component required for connectivity. As a result, your service is running with reduced capacity, and you may experience slower response times or errors when accessing Salesforce features. We are working with our infrastructure teams to restore the missing component and return capacity to normal levels. Additional impacted instances have been identified and have now been added to this messaging. The start time of the issue has been revised to more accurately reflect the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. update2026-01-07 13:27 UTC

   Work is still underway to restore the missing component and remediate the issue. In parallel, we're reviewing whether a recent change may be a trigger of the issue and analyzing logs to better understand the issue. Instances BRA34 and BRA18 have been identified as being impacted and have now been added to this messaging. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. update2026-01-07 13:49 UTC

   A recent release has been ruled out, and currently, a configuration issue is thought to be the trigger of the impact. A configuration change is being implemented in a test environment to check whether this allows new application servers to start, and brings the services back to normal operating levels. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

5. update2026-01-07 14:00 UTC

   Following further analysis, the start time of the issue has been updated to 08:45 UTC, which is when the configuration change occurred. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

6. update2026-01-07 14:06 UTC

   The configuration change has been completed in a test environment and has proved successful. This has been deemed a safe change to implement in production and is now being applied to all affected instances. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

7. update2026-01-07 14:32 UTC

   The deployment of the configuration change to all impacted instances is still underway, and initial validation is showing positive results. Customers will be seeing signs of improvement as the change is gradually implemented. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

8. update2026-01-07 14:58 UTC

   We are continuing to monitor the deployment of the configuration change. We do not have an estimated time for the completion at this time We’ll provide an update in 30 minutes or sooner if additional information becomes available.

9. update2026-01-07 15:16 UTC

   Customers are no longer impacted as of 14:30 UTC. All impacted instances have received the necessary configuration change (including BRA16, which was recently identified as impacted and included in this messaging), and new application servers are now able to start. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab). Salesforce profile · Recent Salesforce incidents · Markdown · JSON