Customer360Audiences Degradation on ARE6, IND8S, IND10S, IND28S…

What to do

• Check whether you use Salesforce Customer360Audiences in are6, ind8s, ind10s, ind28s. 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 1h 16m it lasted.

  Anything that failed between 2026-10-26 12:27 UTC and 2026-10-26 13:43 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

The issue was caused by a code deployment that preceded the required database updates, resulting in a compatibility mismatch.

Category: Deploy or config change

Updates from Salesforce 1

1. updateOct 26, 2026, 2:14 PM UTC

   Data Cloud features dependent on a shared processing service, including segmentation publishing, experienced a period of unavailability. During this time, customers may have observed failed entries in their publish history. The issue was caused by a code deployment that preceded the required database updates, resulting in a compatibility mismatch. The team resolved the issue by applying the pending database and infrastructure updates, restoring service availability and stability. Impacted jobs were rerun where possible, and no customer action was required. We sincerely apologize for the disruption and any impact this incident may have had on your business. A thorough investigation will be conducted to identify the technical trigger, determine the underlying root cause, and implement preventive measures to minimize 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.