# Spiff Degradation on SPIFF-US1 - Provider: [Salesforce](https://down.guide/salesforce) - Level: confirmed - Impact: Degraded - lasted 35d 2h - started 2026-09-14 13:40 UTC - Spiff - spiff-us1 - id: DWN-959f76d1c0 - Official page: https://status.salesforce.com/incidents/20004430 ## Updates from Salesforce ### 2026-09-16 16:32 UTC: investigatingpotentialcause We are investigating a potential cause of the issue. ### 2026-09-18 13:42 UTC: update The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update every two business days or sooner if we have more information. ### 2026-09-21 16:32 UTC: update 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. ### 2026-09-23 20:13 UTC: update 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 ### 2026-09-25 15:45 UTC: update 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. ### 2026-09-28 16:12 UTC: update 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. ### 2026-10-01 18:48 UTC: update 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 ### 2026-10-05 21:18 UTC: update 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 ### 2026-10-07 19:51 UTC: update 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 ### 2026-10-09 15:14 UTC: update 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 ### 2026-10-12 20:15 UTC: update 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. ### 2026-10-13 17:50 UTC: update 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. ### 2026-10-14 16:15 UTC: update 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. ### 2026-10-15 23:27 UTC: update 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. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).