coreService Disruption on USA1226S, USA1228S, USA1230, USA1232

What to do

• Check whether you use Salesforce coreService in usa1226s, usa1228s, usa1230, usa1232. 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 5h 3m it lasted.

  Anything that failed between 2026-10-27 20:59 UTC and 2026-10-28 02:02 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've determined that the issue is not due to a third-party service disruption.

Category: Upstream dependency

Updates from Salesforce 9

1. updateOct 27, 2026, 9:41 PM UTC

   We're aware of an issue impacting multiple Salesforce instances. Since approximately 20:59 UTC, customers on affected instances may have been unable to log in or access their services. We've engaged our third-party partners to assist in the investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

   provider

2. updateOct 27, 2026, 10:00 PM UTC

   We've determined that the issue is not due to a third-party service disruption. We're now investigating recent changes that may be related, and we're working to find the best path to resolution.

   provider

3. updateOct 27, 2026, 10:10 PM UTC

   As a precaution, we've started reverting a recent change to return it to its previous working state, and we're investigating other possible causes.

   provider

4. updateOct 27, 2026, 10:25 PM UTC

   We're still reverting the recent change we identified, and we're continuing to investigate other possible causes.

   provider

5. updateOct 27, 2026, 10:46 PM UTC

   We're still reverting the recent change, and we're now investigating our network infrastructure.

   provider

6. updateOct 27, 2026, 10:59 PM UTC

   We're making progress on rolling back the recent change, and we're also reviewing other recent changes that may be related.

   provider

7. updateOct 28, 2026, 1:09 AM UTC

   We have completed a rollback of the recent network configuration change in a lower environment and are working through the remaining validation steps before applying the update to production. We'll continue to provide updates as our investigation progresses.

   provider

8. impactradiusincreaseOct 28, 2026, 1:38 AM UTC

   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

9. updateOct 28, 2026, 2:41 AM UTC

   Once we successfully completed the validation steps in the lower environment, and confirmed connectivity was restored. We applied the same fix to the production environment and confirmed customers on affected instances can now log in and access their services. This issue is now resolved. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

   provider

Corrections

None so far.

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