- Level
- confirmed
- Worst impact
- Degraded
- Components
- Agentforce, Customer360Audiences
- Regions
- usa1, usa2s, usa3s, usa80s, usa220, usa228, 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, usa642, usa714, usa794, usa856, usa870s, usa872s, usa874s, usa876, usa920, usa948s, usa950s, usa960, usa994, usa1012, usa1016, usa1018, usa1022, usa1024, usa1026, usa1028, usa1030, usa1032, usa1034, usa1036s, usa1038, usa1074s, usa1076s, usa1078, usa1082, usa1088s, usa1092, usa1112, usa1122, usa1126, usa1148s, usa1176, usa1206s, usa1208s, usa1260s, usa1262s, usa1264s, usa1266s
- Down Index
- 43of 100
What to do
Check whether you use Salesforce Agentforce, Customer360Audiences in usa1, usa2s, usa3s, usa80s. 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 1d 15h it lasted.
Anything that failed between 2026-10-06 06:00 UTC and 2026-10-07 21:45 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 10
- update
We're investigating an issue affecting Data 360 where a subset of customers running SQL queries against their data in Data 360 may experience errors or delays. Customers are also unable to view Data Lake Object (DLO) and Data Model Object (DMO) data in Query Editor. We have restarted the affected components and are monitoring the services. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
We’ve confirmed that restarting the affected components resolved the issue. Data 360 services are now working as expected including access to Data Lake Object (DLO) and Data Model Object (DMO) data in Query Editor. Our investigation also confirmed that the impact was broader than initially identified and we have updated this incident to reflect the full scope of the impact. We apologize for how this incident affected you and your business.
provider
- update
Upon further investigation, we’ve determined that the end time of the impact is different than initially understood. We’ve revised the end time of the Trust post to more accurately reflect when the issue was resolved for customers. We apologize for any confusion.
provider
- update
We’ve become aware that a subset of customers are continuing to experience errors when viewing certain records within Salesforce. We've identified the trigger as stale cached data remaining from the earlier issue and are running a process to clear the affected data and restore normal service. This process is expected to take a few hours to complete. We'll provide another update as additional information becomes available.
provider
- update
We’re continuing the process to clear the affected data and restore normal service. In the meantime, we've also published a Known Issue article containing workaround steps that affected customers can follow to view the impacted records. Known Issue Article: https://help.salesforce.com/s/issue?id=a02g700000BAWcz We'll provide another update as additional information becomes available.
provider
- update
We’re continuing our efforts to clear the affected data to restore normal service. The data refresh is nearly complete and we are still clearing cached data that can cause errors. Some customers may still see intermittent errors when viewing Data Lake Objects until the cleanup completes. The Known Issue article remains available with workaround steps: https://help.salesforce.com/s/issue?id=a02g700000BAWcz We’ll continue monitoring the recovery and share further updates as progress is made.
provider
- update
The metadata refresh in lakehouse is complete. We’re continuing to make steady progress with clearing the cached metadata. We’re running this process at a measured pace to protect the service for all customers. Some customers may still see intermittent errors when viewing Data Lake Objects until the cleanup finishes. We’ll continue monitoring and share further updates as progress continues.
provider
- update
The metadata refresh in lakehouse is complete. We’re continuing to make steady progress with clearing cached metadata. We’re running this process at a measured pace to protect service for all customers. Some customers may still see intermittent errors when viewing Data Lake Objects until the cleanup finishes. We’ll continue monitoring and share further updates as progress continues.
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
The cached metadata has now been cleared. After a period of monitoring, we have confirmed that access to Data Lake Objects is restored for all affected customers. We apologize for the impact on our customers and their businesses. A full investigation will determine the technical trigger and underlying cause, and how we prevent this from happening again.
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-25567c3235
Is Salesforce still down?
No, this incident was resolved 2026-10-07 21:45 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
1d 15h, from 2026-10-06 06:00 UTC to 2026-10-07 21:45 UTC, by the times Salesforce posted.
What was affected?
Salesforce named Agentforce, Customer360Audiences in usa1, usa2s, usa3s, usa80s.
What caused it?
Salesforce hasn't published a root cause. If it does, it shows here.
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.