Skip to main content
Salesforce

coreService Degradation on CS238, CS241, CS243, CS244…

Major outage Lasted 1d 4h · started · Salesforce's page

Level
confirmed
Worst impact
Major outage
Components
coreService
Regions
cs238, cs241, cs243, cs244, cs245, cs246, cs251, cs252, cs254, cs255, cs264, cs275, cs283, cs329, cs339, na223, na224, na225, na233, na234, na236, na237, na239, na240, na242, na243, na244, na246, na247, na248, na249, na251, na252, na254
Down Index
65of 100

What to do

  • Check whether you use Salesforce coreService in cs238, cs241, cs243, cs244. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1d 4h it lasted.

    Anything that failed between 2026-10-07 18:00 UTC and 2026-10-08 22:21 UTC may need a replay.
  • Subscribe to Salesforce's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=salesforce works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

We apologize for any confusion caused by this.
Read the postmortem

Updates from Salesforce 7

  1. update

    We’re investigating an issue affecting CRM Analytics recipe execution for a subset of customers. Affected customers may be unable to run their recipes. The issue is limited to certain Salesforce-hosted environments, and Hyperforce environments are not affected. We’ve identified that a required processing component is unavailable in some affected environments following a recent deployment. We’re working to restore the component and resume normal recipe execution. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

    provider

  2. update

    We're continuing to investigate the issue affecting CRM Analytics recipe runs for a subset of customers. Our teams identified a potential fix and are currently testing it on a limited scope before rolling it out further. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

    provider

  3. impactradiusincrease

    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.

    provider

  4. starttimerevision

    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.

    provider

  5. update

    We're testing a rollback of a recent change on a limited scope to confirm it resolves the issue affecting CRM Analytics recipe runs. Once validated, we'll assess rolling the fix out further. We'll provide an update upon completion of the initial deployment or sooner if additional information becomes available.

    provider

  6. update

    Rollback testing was successful, and we are now proceeding to apply this rollback change across the remaining affected environments. Additionally, investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not 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 upon completion of the deployment or sooner if additional information becomes available.

    provider

  7. update

    We’ve resolved an issue affecting CRM Analytics recipe runs for a number of customers, preventing recipes from completing successfully. We rolled back the affected service to a prior stable version, and recipe runs have now returned to normal. 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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-bc51047608

Is Salesforce still down?

No, this incident was resolved 2026-10-08 22:21 UTC. For Salesforce's live state, see https://down.guide/salesforce.

How long did it last?

1d 4h, from 2026-10-07 18:00 UTC to 2026-10-08 22:21 UTC, by the times Salesforce posted.

What was affected?

Salesforce named coreService in cs238, cs241, cs243, cs244.

What caused it?

Salesforce wrote: "We apologize for any confusion caused by this." The postmortem: https://status.salesforce.com/incidents/20004479

Where does this come from?

Salesforce's official status page, https://status.salesforce.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.