coreService Degradation on JPN170

What to do

• Check whether you use Salesforce coreService in jpn170. 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 4h 42m it lasted.

  Anything that failed between 2026-11-02 13:20 UTC and 2026-11-02 18: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.

Updates from Salesforce 3

1. investigatingcauseofissueNov 2, 2026, 4:49 PM UTC

   We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

   provider

2. implementingsolutionworkingonfixNov 2, 2026, 5:05 PM UTC

   We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

   provider

3. updateNov 2, 2026, 7:09 PM UTC

   We’ve implemented the fix, and performance has returned to normal. During this incident, customers may have experienced difficulty querying recently updated or created records. 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

Corrections

None so far.

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