- Level
- confirmed
- Worst impact
- Major outage
- Components
- Customer360Audiences, analytics
- Regions
- bra6s, bra18, bra34, bra36, bra44, bra50, can26, cs236, cs237, cs252, na223, na232, na233, na235, na236, na238, na241, na242, na243, na244, na246, na247, na252, na253, usa1, usa2s, usa3s, usa80s, usa220, usa240s, usa242s, usa244s, usa248s, usa250s, usa252s, usa254s, usa256s, usa258s, usa260s, usa312, usa314, usa316, usa318, usa320, usa322, usa324, usa326, usa328, usa330, usa332, usa334, usa336, usa338, usa340, usa342, usa344, usa346, usa348, usa350, usa352, usa354, usa356, usa358, usa360, usa366s, usa372, usa374, usa376, usa384, usa688, usa710s, usa716, usa722, usa732, usa744, usa746, usa748, usa754s, usa778, usa794, usa842, usa844, usa856, usa862, usa870s, usa872s, usa874s, usa876, usa920, usa948s, usa950s, usa960, usa994, usa1012, usa1016, usa1018, usa1022, usa1024, usa1026, usa1028, usa1030, usa1032, usa1034, usa1036s, usa1038, usa1044, usa1052, usa1074s, usa1076s, usa1078, usa1082, usa1088s, usa1092, usa1112, usa1122, usa1126, usa1140, usa1142, usa1148s, usa1154s, usa1160, usa1176, usa1188, usa1192, usa1206s, usa1208s, usa1260s, usa1262s, usa1264s, usa1266s, usa1268, usa1290, usa1336
- Down Index
- 65of 100
What to do
Check whether you use Salesforce Customer360Audiences, analytics in bra6s, bra18, bra34, bra36. 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 13h 10m it lasted.
Anything that failed between 2026-10-04 11:15 UTC and 2026-10-05 00:25 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 have identified an issue related to high memory utilization due to an underlying service.Read the postmortem
Updates from Salesforce 12
- update
At 11:15 UTC on October 4, 2026, a feature disruption began impacting CRM Analytics in the production environment. As a result, customers in the affected environment are unable to use CRM Analytics, and their CRM Analytics jobs are failing. We are investigating the issue and analyzing data to determine the best path to resolution. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
We have identified an issue related to high memory utilization due to an underlying service. We are exploring multiple paths to isolate the underlying cause of the issue and implement a fix to restore the services. We are reviewing the error logs and diagnostic information. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
We remain engaged and will continue to determine the best path to resolution. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
provider
- update
We have identified a potential trigger of the issue and are reviewing additional logs. In parallel, we are working on allocating additional resources to accommodate for increased memory utilization as an interim fix. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
provider
- update
We're continuing to work on restoring service for CRM Analytics customers on the affected instances. Our investigation found that a supporting service used during startup is slow to respond. We've applied configuration changes and are raising a request limit on that service. We'll provide the next update once additional information becomes available.
provider
- update
We continue to work on mitigation to restore service for CRM Analytics customers. Some customers may still see failures or delays when running recipes. We'll provide an update once additional information becomes available.
provider
- update
We continue to work on mitigation to restore service for CRM Analytics customers. Some customers may still see failures or delays when running recipes. We're working with other teams to identify the source of the increased load. We'll provide an update after additional information becomes available.
provider
- update
We continue to work on mitigation to restore service for CRM Analytics customers. We're taking steps to reduce the load on the affected service. Some customers may still see failures or delays. We'll provide an update after additional information becomes available.
provider
- update
We've identified that Data Cloud customers are also affected. Some Data Cloud ingestion and segmentation tasks may fail or be delayed, in addition to CRM Analytics recipe runs. We continue to work on mitigation to restore service for both. We'll provide an update once additional information becomes available.
provider
- impactradiusincrease
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
- update
We've completed the recovery steps on the affected internal services. CRM Analytics recipe runs are starting to succeed, and we're monitoring to confirm full recovery. Additionally, we're working to restore Data 360 segmentation tasks. We’ll provide an update as additional information becomes available.
provider
- update
We increased capacity on the affected internal services and restarted them, which restored normal operation at 00:25 UTC on October 5, 2026. CRM Analytics recipe runs and Data 360 segmentation tasks are running successfully, and we resolved the issue. Customers may need to run any tasks that failed or were delayed during the disruption. We apologize for how your 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-06a2310c06
Is Salesforce still down?
No, this incident was resolved 2026-10-05 00:25 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
13h 10m, from 2026-10-04 11:15 UTC to 2026-10-05 00:25 UTC, by the times Salesforce posted.
What was affected?
Salesforce named Customer360Audiences, analytics in bra6s, bra18, bra34, bra36.
What caused it?
Salesforce wrote: "We have identified an issue related to high memory utilization due to an underlying service." The postmortem: https://status.salesforce.com/incidents/20004466
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.