Is Salesforce down?

Disruption Started: serviceDisruption

We're investigating an issue impacting multiple instances across all regions where customers may experience severe delays, intermittent errors, or an inability to access some services. Some customers are also unable to submit new support cases through the Help portal. We're investigating the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Investigations indicate that requests are stalling while waiting on a response from an internal login service, which is using up available server resources. Customers continue to experience severe delays, intermittent errors, and inability to access some services. This also affects support case creation. We've attempted a rolling restart on one of the impacted instances to see if that resolves the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We believe that the issue is caused by an external dependency failure that's impacting the legacy login server. We're blocking the Application Programming Interface (API) endpoint as a potential mitigation step. We also engaged our third-party infrastructure provider to determine if there are any issues and they've confirmed that there are no issues with ‌third-party infrastructure. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're no longer pursuing restarts as a path to remediation. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

One of our core system components experienced increased load, which limited its capacity to process requests. We're working on a fix to resolve this issue and restore services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're pursuing the fastest path to restore services. We're testing our fix on a test instance. Once the test is validated, we'll roll out the fix fleetwide. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've validated the fix successfully on the test instance. We'll now roll out the fix fleetwide to all impacted instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.

A fleetwide rollout is in progress and customers are starting to see their service return to normal. In parallel, we're working on a code-level permanent fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

The rollout is progressing region by region and we're seeing improvement. We don't have a confirmed time of completion. GovCloud customers have been confirmed to be out of impact. Customers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

The rollout is progressing region-wise and services are returning to normal in regions that are completed. We're monitoring the rollout as it continues, and we're working on a permanent fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

As the rollout is progressing region-wise, most instances are recovering. Some customers may still see errors accessing the service until we finish a manual restart on their instance. We don't have a confirmed resolution time. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've determined that the rollout didn't fully complete for a number of instances, so some customers may still be experiencing the original issue. We're reapplying the fix now. Some customers may need to clear cached data or restart their session for full recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've completed the next phase of the rollout. We're manually restarting ‌instances where the automated fix didn't fully resolve the issue. We’ve received reports of scheduled jobs not running as expected for some customers who are now able to access the service. We're investigating this. Investigations have highlighted that the impact radius is narrower than initially understood. We'll now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've completed the next phase of the rollout to the remaining impacted instances. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. Customers who are affected may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're seeing signs of recovery and many customers are coming out of impact. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. We don't have a confirmed resolution time. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve narrowed the remaining impact to a subset of Hyperforce instances. First-party environments were not impacted. The mitigation is now in place across nearly all affected instances, and we’re completing targeted restarts and manual recovery actions on the remaining affected instances. Some customers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.

We’ve completed applying the mitigation across the affected Hyperforce environments and are conducting fleetwide validation to confirm service recovery. Most customer-facing impact has cleared, while we work through a small number of remaining instances that require additional verification or targeted recovery actions. Customers on any remaining affected instances may continue to experience severe delays, intermittent errors, or difficulty accessing some services and creating support cases. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Our telemetry is no longer showing active performance or availability impact across customer-facing Hyperforce environments. We’re validating recent customer reports against service health data and confirming the recovery time before declaring the issue resolved. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Service telemetry has remained healthy across customer-facing Hyperforce environments since 15:26 UTC. Our review of recent customer reports has not identified any confirmed ongoing impact related to this incident. The mitigation remains active, and we’re applying additional preventive protections to related service paths while completing final validation. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

We continue to observe healthy service telemetry across customer-facing Hyperforce environments, and our review of recent customer reports has not confirmed ongoing impact related to this incident. We’re completing validation of one isolated report before declaring the issue resolved. The mitigation remains active, and we’re adding preventive protections to related service paths to reduce the risk of recurrence. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

Service telemetry remains healthy, and our review has not confirmed any ongoing customer impact related to this incident. Before declaring the issue resolved, we’re ensuring the existing mitigation remains active across all affected customer-facing Hyperforce environments. We’re applying targeted updates where the automated process did not complete, helping maintain service stability and reduce the risk of impact returning. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

Degradation Started: salesforceSpiffFeatureDisruption

We are investigating a potential cause of the issue.

We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.

Degradation Started: featurePerfDegradation

We’re investigating an issue affecting Agentforce session scoring and tagging functionality for a subset of customers. Our teams are actively working to identify the trigger and restore service. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We’re continuing to investigate an issue affecting Agentforce session scoring and tagging for a subset of customers. Our teams are analyzing processing failures and reviewing affected customer environments to determine the trigger and identify a path to restore functionality. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Our teams have narrowed the investigation to failures occurring during session processing and are working to identify a path to restore functionality. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

We have identified a potential fix and are preparing to apply it to affected customer environments. We’ll monitor session tagging performance following the change to determine whether functionality recovers while our investigation into the underlying issue continues. We’ll provide another update as significant progress is made.

Degradation Started: featureServiceDisruption

We're aware of the issue affecting credit card transactions on Commerce Cloud, where customers are unable to complete purchases using credit cards at checkout. We're restarting the affected applications to restore transaction processing and working on a broader fix to resolve this for all impacted customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

We've applied manual fixes across all known affected environments to restore credit card transaction processing on Commerce Cloud checkouts. We're now testing an automated, fleet-wide fix to fully resolve this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Degradation Started: agentforcePerformanceDegradation

The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. Thank you for your patience as we work to resolve this issue.