Companies / Salesforce / incidents

Salesforce: Performance Degradation: Core Service

Impact: minorStatus: resolvedStarted Resolved (9.9 h)9 updatesSource: status.salesforce.com (opens in new tab)

Affected components: Core Service12 instances

Timeline of updates

  1. update

    We're investigating an issue where customers are experiencing elevated processing delays and a database overload impacting multiple instances in the eu-west-3, and eu-central-1 regions, triggered by a recent change. We're actively working to reduce database load and restore normal processing. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

  2. update

    Customers are experiencing high wait times, with message queue (MQ) processing halted on impacted instances. Investigations have highlighted that the impact radius is broader than initially understood. We've updated the posting to reflect ‌additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

  3. update

    Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

  4. update

    Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove USA80S, USA244S, USA252S, and USA876 that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

  5. update

    We're continuing to work to reduce database load and restore normal processing by addressing problematic jobs on the impacted instances. We apologize for how you and your business ‌may be affected by this incident. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

  6. update

    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.

  7. update

    We're actively addressing the problematic jobs on the impacted instances and are seeing signs of service recovery. As a preventive measure, we will terminate non-essential background jobs to avoid further degradation and support continued stabilization. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

  8. update

    We're seeing signs of recovery as we address the ‌problematic jobs on the FRA instances, while a subset of customers on the remaining impacted instances may continue to experience high wait times with message queue (MQ) processing halted. Investigations have highlighted that the impact radius is broader than initially understood. We've updated this posting to reflect ‌additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

  9. update

    We’ve resolved an issue impacting the eu-west-3, and eu-central-1 regions by addressing the problematic jobs that were suspended by post-processing followed by health checks. Services have been restored as of 11:30 UTC and customers should no longer experience any impact. Investigations have highlighted that the impact radius is broader than initially understood. We've updated this posting to reflect ‌additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. We'll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.

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