Salesforce Outage History

Salesforce Spiff experienced a feature degradation affecting statement calculations, reporting, designer, connectors and syncs for approximately 15 days. Users encountered a visual bug where the recalculate button's calculator icon would spin indefinitely and the "Calculated at" timestamp wouldn't update, though calculations continued to function normally behind the scenes. The issue was resolved with a page refresh workaround while the underlying problem was addressed.

Salesforce experienced performance degradation affecting components GBR120 and SWE26 for 3.9 hours, causing slow performance, timeouts, and connectivity issues while some functionality remained unavailable or suboptimal. The Salesforce Technology team identified a potential trigger for the issue and implemented a fix to resolve the degradation.

Salesforce Data Cloud experienced a feature degradation affecting the USA424 component for 1.1 hours. Some features were unavailable or performed below optimal levels during this incident. The team actively monitored and worked to restore full service functionality.

Salesforce experienced performance degradation affecting component NA253 for 1.9 hours, causing slow performance, timeouts, and connectivity issues for users. The Salesforce Technology team identified a database issue as the root cause and performed a database failover from primary to secondary systems, which temporarily disrupted service access for 10-15 minutes. The failover process successfully resolved the performance issues, with the team monitoring for any residual degradation afterward.

Salesforce experienced a feature degradation in Marketing Cloud Intelligence affecting the Analyze & Act pivot table functionality for 18.7 hours. Users could still access the service but experienced reduced performance and unavailable functionality in this specific section. The Salesforce Technology team investigated and resolved the issue.

Salesforce experienced a feature disruption lasting 35.9 hours that prevented users from saving changes to event records, particularly affecting customers using Einstein Activity Capture who encountered error messages when updating existing events. The issue was caused by a specific feature that was initially disabled to prevent further impact, followed by a code-level fix that was rolled out in a staggered manner across affected instances. The fix was successfully deployed to many instances, with separate validation and communication provided for each affected environment.

Tableau Cloud experienced a feature degradation lasting 50.5 hours where extract refresh jobs failed across multiple PODs, particularly affecting customers using SharePoint Lists JDBC when OAuth connections expired. Engineers identified a recent change as the root cause and deployed a fix across all affected instances in a staggered rollout. The fix has been successfully deployed and the team is monitoring system performance to ensure continued stability.

Salesforce experienced a service disruption affecting email routing functionality, including Email-to-Case and Email-to-Apex features, across multiple global instances spanning Australia, India, Japan, Singapore, France, USA, UK, Korea, Sweden, UAE, Switzerland, and Indonesia. Users were unable to create cases through Email-to-Case as emails sent to configured addresses were not being received, and all email-to-Salesforce routing services were impacted. The issue was resolved after 3.8 hours through a complete rollback of a recent infrastructure deployment, with email functionality restored and queued emails being processed.

Salesforce Data Cloud experienced a feature degradation lasting 3.9 hours, causing some features to become unavailable or perform below optimal levels across multiple instances including CAN2S, AUS26S, DEU10S, DEU36, USA474, SWE82, and several USA instances. The team implemented a solution and continued monitoring instance performance levels to ensure full restoration.

Salesforce Data Cloud experienced a feature degradation lasting 7.8 hours, specifically impacting the live query federation feature across multiple instances including USA3S, USA242S, USA250S, USA256S, USA330, USA372, GBR82, and USA872S. The Salesforce Technology team identified the trigger and implemented fixes including increased memory allocation for an impacted component, which provided partial relief, followed by additional deployments to further reduce the impact.