coreService Disruption on USA864

What to do

• Check whether you use Salesforce coreService in usa864. 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 2h 15m it lasted.

  Anything that failed between 2026-10-23 01:25 UTC and 2026-10-23 03:40 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 will conduct a thorough investigation to determine the technical trigger, identify the underlying root cause, and implement preventive measures to reduce the risk of recurrence.

Updates from Salesforce 1

1. updateOct 23, 2026, 5:20 AM UTC

   We have resolved the issue that prevented users from logging in and accessing their orgs. We identified an issue introduced by a recent release that disrupted the creation of login sessions. We rolled back the affected release and confirmed that access has been restored. Users can now log in and access their orgs. We sincerely apologize for the disruption and its impact on your business. We will conduct a thorough investigation to determine the technical trigger, identify the underlying root cause, and implement preventive measures to reduce the risk of recurrence.

   provider

Corrections

None so far.

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