rewindex

CompaniesSalesforceIncidents

Salesforce: Service Disruption: Core Service

MajorStatus: resolvededitedStarted Resolved (7.3 h)19 updatesstatus.salesforce.com (opens in new tab)
Summary

Salesforce reported a major Core Service disruption affecting 3 instances starting 2026-10-23 01:25 UTC; affected users could not log in to their org and saw an error message. It remained open when archived, 1 h 26 min at the last update; Salesforce was restarting servers in stages to restore access and investigating the cause.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Core Service1 instance

Timeline of updates

  1. update

    We've confirmed that affected users can't log in to their org and see an error message. We began restarting our servers in stages to restore access. We're continuing to investigate the cause. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

  2. 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.

  3. update

    Affected users can't log in, and attempts to open orgs return an internal server error. We're continuing to investigate the trigger. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  4. 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.

  5. update

    We’ve identified a mismatch between a recent application update and a database change, stopping users from logging in. We’re planning to roll back the update across impacted instances. We’re also preparing to test a newer version on one of impacted instance to validate whether it restores user access.
    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 confirmed that we restored access on one impacted instance by rolling back a recent application update. At 03:57 UTC, we began deploying a newer version to a second impacted instance to validate the fix. Once validation is complete, we plan to roll out the fix to the remaining impacted instances.
    Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs.
    We’ll provide the next update within 30 minutes, or sooner if new information becomes available.

  8. update

    We confirmed that a fix forward has restored access on the second impacted instance USA1072 at 04:11 UTC. We're now preparing to deploy this fix forward to the remaining impacted instances. Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs.

    We'll post a separate Trust update for each instance that receives the fix, so each shows an accurate end time
    We'll provide an update in 30 minutes or sooner if additional information becomes available.

  9. update

    We have identified the fix-forward deployment as our path to full recovery and are expediting its rollout across all remaining impacted instances. Deployment is currently underway across multiple instances, and we do not yet have an estimated time for completion.
    Users on instances that have not received the updated version may continue to experience issues logging in or accessing their orgs.
    We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available.

  10. update

    We continue to prioritize restoring access across all remaining impacted instances. We are actively deploying the identified fix across multiple instances, with the fix-forward deployment remaining our path to full recovery.
    The rollout is still in progress, and we are closely monitoring deployment progress and validating recovery as each instance receives the updated version. While we are working to complete the rollout as quickly as possible, we do not yet have an estimated time for full recovery.
    Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs
    .We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available.

  11. update

    The fix-forward deployment is progressing well across the remaining impacted instances, and our teams continue to prioritize restoring access as quickly as possible. We are closely monitoring the rollout and validating recovery as each instance receives the updated version.
    We have removed recovered instances from the main incident post to accurately reflect their respective impact end times. We will continue to provide instance-specific recovery updates as deployment progresses.
    Users on instances that have not yet received the fix may continue to experience issues logging in or accessing their orgs. While deployment is progressing, we do not yet have an estimated time for full recovery.
    We will provide our next update in 30 minutes, or sooner if additional information becomes available.

  12. update

    Our investigation has confirmed that the scope of impact is narrower than initially identified. We have verified that instance USA594 was not affected by this incident and have removed it from the list of impacted instances. As a result, this instance will no longer receive incident-related communications.

    We will continue to provide updates for the remaining impacted instances as we work toward full recovery.

    We apologize for any confusion caused by the earlier inclusion of this instance.

  13. update

    We continue to make steady progress with the fix-forward deployment across the remaining impacted instances. Our teams are actively rolling out the fix-forward and verifying that users can successfully log in and access their orgs as each instance recovers.
    As we confirm recovery, we are removing the affected instances from the main incident post to accurately reflect their respective impact end times. We will continue to share instance-specific updates as we validate recovery.
    Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. Although the deployment is progressing as expected, we do not yet have an estimated time for full recovery.
    Restoring access across all remaining impacted instances remains our highest priority. We will provide our next update in 30 minutes, or sooner if additional information becomes available.

  14. update

    The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances and validating that users can successfully log in and access their orgs.
    As we confirm recovery, we continue to update the incident scope and remove recovered instances from the main incident post to accurately reflect their respective impact end times. We will communicate recovery through instance-specific updates.
    Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion.
    We will provide our next update in 30 minutes, or sooner if additional information becomes available.

  15. update

    We have verified that instances IND116, USA326, USA938s, and USA1230 were not affected by this incident and have removed it from the list of impacted instances. As a result, these instances will no longer receive incident-related communications.

    We will continue to provide updates for the remaining impacted instances as we work toward full recovery. We apologize for any confusion caused by the earlier inclusion of this instance.

  16. update

    The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances.

    We're continuing to provide recovery confirmation and accurate resolved timestamps for instances via separate postings.

    Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available.

  17. update

    The fix-forward deployment continues to progress across the remaining instances. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion.

    We will provide our next update in 30 minutes, or sooner if additional information becomes available.

  18. update

    The fix-forward deployment continues to progress across the remaining instance. Users on instance awaiting the fix may continue to experience issues logging in or accessing their orgs.

    We will provide our next update in 30 minutes, or sooner if additional information becomes available.

  19. update

    We have resolved an issue that prevented users from logging in. We identified an issue with a recent release that prevented login sessions from being created. We deployed a fix forward, and access is now restored. Users can log in and open their orgs again.

    We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).

Cite this

Status incident (vendor impact label: major) posted by Salesforce, started 2026-10-23 01:25 UTC, resolved after 7.3 h, 19 update(s); edited after publishing.

Title
Service Disruption: Core Service
Vendor
Salesforce
Date
URL
https://rewindex.com/company/salesforce/incidents/20004512

Salesforce profileRecent Salesforce incidentsAll outages on October 23, 2026Salesforce in October 2026MarkdownJSON