Companies / Salesforce / incidents
Salesforce: Performance Degradation: Core Service
Affected components: Core Service584 instances
Timeline of updates
- update
We are investigating a performance degradation where a subset of customers are experiencing issues logging into Salesforce services when using single sign-on (SSO) with Okta Verify/Salesforce Identity Provider (IDP). Initial investigations indicate that a recent release may be the potential trigger. We are actively working to identify the full extent of impact and the best path to remediation. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- 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.
- update
We are currently rolling back the change on a test instance to determine whether it resolves the issue. If successful, we will proceed with rolling back the change on the remaining impacted instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- update
The rollback completed and has been verified to have resolved the issue on USA694. We are conducting the rollback on another test instance prior to initiating the rollback on the remaining impacted instances. If successful, we will proceed with rolling back the change to all impacted instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- update
The rollback on USA414 was successful and we are now proceeding with a targeted rollback for the remaining impacted instances. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- update
We are seeing signs of recovery and some customers are seeing success logging into Salesforce services using single sign-on (SSO) with Okta Verify/Salesforce Identity Provider (IDP). Targeted rollbacks are still in progress. Upon further investigation, we’ve determined that the start time of the impact is different than initially understood. We have now 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. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- update
We're currently progressing with the rollback across the remaining instances. In parallel, we're actively monitoring performance and optimizing systems to ensure sustained recovery. We'll provide an update in 90 minutes or sooner if additional information becomes available.
- update
We're actively monitoring the rollback progress across the remaining instances. We'll provide an update upon completion of the rollback.
- update
After monitoring performance and completing health checks, we have confirmed that services have been restored as of 23:58 UTC, February 3 following a rollback of the recent change. Investigations have highlighted that the impact radius is different than initially understood. We have updated the posting to add the additional instances that experienced impact, and removed instances that did not experience impact. We will 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.
- update
This incident is resolved as of 23:58 UTC, February 3. Upon further investigation, a number of additional instances were identified as impacted, and these have now been included in this Trust post. We apologize for any inconvenience this has caused to our customers.
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