Salesforce incident
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
Salesforce experienced a minor incident on October 6, 2026 affecting USA1 and USA1012 and 1 more component, lasting 1d 11h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 06, 2026, 10:07 AM UTC
Degradation Started: featurePerfDegradation
- monitoring Oct 06, 2026, 10:22 AM UTC
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.
- monitoring Oct 06, 2026, 10:41 AM UTC
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.
- monitoring Oct 06, 2026, 10:55 AM UTC
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.
- monitoring Oct 06, 2026, 03:27 PM UTC
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.
- monitoring Oct 06, 2026, 03:58 PM UTC
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://sfdc.co/AEACbx We'll provide another update as additional information becomes available.
- monitoring Oct 07, 2026, 02:41 AM UTC
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.
- monitoring Oct 07, 2026, 08:38 AM UTC
The data refresh is complete. We’re continuing to make steady progress with clearing the cached data. 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.
- monitoring Oct 07, 2026, 12:11 PM UTC
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.
- monitoring Oct 07, 2026, 05:13 PM 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.