Salesforce incident
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
Salesforce experienced a minor incident on September 14, 2026 affecting SPIFF-US1, lasting 34d 22h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 14, 2026, 05:11 PM UTC
Degradation Started: salesforceSpiffFeatureDegradation
- monitoring Sep 16, 2026, 04:32 PM UTC
We are investigating a potential cause of the issue.
- monitoring Sep 18, 2026, 01:42 PM UTC
We are investigating a potential cause of the issue.
- monitoring Sep 21, 2026, 04:32 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- monitoring Sep 23, 2026, 08:13 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- monitoring Sep 25, 2026, 03:45 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- monitoring Sep 28, 2026, 04:12 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- monitoring Oct 01, 2026, 06:48 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- monitoring Oct 05, 2026, 09:18 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- monitoring Oct 07, 2026, 07:51 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- monitoring Oct 09, 2026, 03:14 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- monitoring Oct 12, 2026, 08:15 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- monitoring Oct 13, 2026, 05:50 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- monitoring Oct 14, 2026, 04:15 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- monitoring Oct 15, 2026, 11:27 PM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.