Skip to main content
Salesforce

coreService, liveAgent Degradation on USA1152S, USA1158, USA1160, USA1348

Degraded Lasted 3h 35m · started · Salesforce's page

Level
confirmed
Worst impact
Degraded
Components
coreService, liveAgent
Regions
usa1152s, usa1158, usa1160, usa1348
Down Index
36of 100

What to do

  • Check whether you use Salesforce coreService, liveAgent in usa1152s, usa1158, usa1160, usa1348. 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 3h 35m it lasted.

    Anything that failed between 2026-10-23 11:30 UTC and 2026-10-23 15:05 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.

Updates from Salesforce 1

  1. resolvedperformancedegradation

    We’ve confirmed that the solution implemented to mitigate the issue causing the performance degradation was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate 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.

    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-b335f9ec79

Is Salesforce still down?

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

How long did it last?

3h 35m, from 2026-10-23 11:30 UTC to 2026-10-23 15:05 UTC, by the times Salesforce posted.

What was affected?

Salesforce named coreService, liveAgent in usa1152s, usa1158, usa1160, usa1348.

What caused it?

Salesforce hasn't published a root cause. If it does, it shows here.

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.