Salesforce incident
We've applied a fix to add a missing configuration setting to affected servers and are restarting them to restore full capacity. Customers may experience a brief increase in background system activity
Salesforce experienced a minor incident on October 8, 2026 affecting USA1056 and USA1072 and 1 more component, lasting 1h 58m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 08, 2026, 02:00 PM UTC
Degradation Started: performanceDegradation
- monitoring Oct 08, 2026, 02:31 PM UTC
We've identified that new servers are failing to start because required startup files are missing. As a result, we can't add the capacity needed to handle customer traffic, and some customers may experience slow responses or errors. We're reviewing settings and testing fixes on the affected servers. We'll provide an update in 30 minutes, or sooner if we have more information.
- monitoring Oct 08, 2026, 02:48 PM UTC
We've tested a fix to restore a missing configuration setting on new servers and are preparing to apply it. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Oct 08, 2026, 02:55 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.
- monitoring Oct 08, 2026, 03:24 PM UTC
We've applied a fix to add a missing configuration setting to affected servers and are restarting them to restore full capacity. Customers may experience a brief increase in background system activity as servers restart. We'll provide an update in 30 minutes or sooner if additional information becomes available.