Salesforce Outage History

Tableau Cloud experienced a major service disruption lasting 1.9 hours that prevented end users from accessing the service. Salesforce engineers worked to resolve the issue, with customers beginning to see intermittent improvements during the incident. The service was restored with continued monitoring to ensure performance levels remained stable.

Salesforce experienced a 45.8-hour feature degradation affecting the Agentforce Data Library service across multiple global instances, preventing some customers from creating new data libraries while existing ones continued to function normally. The issue was traced to a recently enabled feature, and the impact radius expanded beyond initial estimates as investigations progressed. Salesforce implemented a fix-forward solution deployed in a staggered rollout outside regional business hours to resolve the degradation.

Salesforce experienced a 6-minute performance degradation affecting component USA654S, causing slow performance, timeouts, and connectivity issues for users. While users could still access the service, some functionality was unavailable or running below optimal performance. The incident was resolved after investigation into the root cause.

Salesforce experienced a 2-hour performance degradation incident affecting components NA225, CS338, and NA242, where users encountered slow performance, timeouts, connectivity issues, and some were unable to log into their environments. The issue was triggered by a recent release, which the team identified and rolled back to resolve the problem. The impact radius was later determined to be narrower than initially assessed, with only a subset of customers actually affected.

Salesforce experienced performance degradation affecting the USA614 component for 1.1 hours. Users could access the service but encountered slow performance, timeouts, connectivity issues, and some unavailable functionality. The incident was classified as minor with general and intermittent performance issues throughout the affected period.

Salesforce experienced a feature disruption lasting 2.1 hours that affected CRM Analytics recipe jobs across multiple US instances, preventing users from obtaining new certificates and accessing specific service features. The incident impacted a broad scope of instances and required manual resource limit increases after an initial service restart failed to resolve the issue. Technical teams investigated recent changes and worked to restore normal operations across the affected components.

Salesforce experienced performance degradation affecting component SWE82 for 25 minutes. Users could access the service but encountered slow performance, timeouts, connectivity issues, and some unavailable functionality. The incident was classified as minor and has been resolved.

Salesforce experienced a major service disruption lasting 4.2 hours that prevented end users from accessing the service. The incident required investigation to determine the root cause. The service was eventually restored, though the specific resolution details were not detailed in the final updates.

Salesforce experienced a Change Data Capture (CDC) feature degradation starting March 10, 2026, when a system update generated an excessive number of events, creating backlogs across multiple instances and causing event notifications to be delayed, missing, or out of order. The incident affected multiple global instances including USA660S, with most instances recovering after teams paused the message queue job causing the event surge. The final affected instance (USA660S) was resolved after 257.5 hours of degraded service.

Salesforce experienced performance degradation affecting multiple regions (BRA18, GBR56, SWE14, USA364, USA614, USA742, USA744) for 5.4 hours, with users encountering slow performance, timeouts, and connectivity issues. The issue specifically impacted the Salesforce Field Service mobile app, causing multi-second delays and slow loading times when opening actions or flows, affecting iOS users starting March 10 and Android users starting March 11. Salesforce identified a recent release as the potential trigger and worked on both fix-forward and rollback resolution options.