Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Salesforce Outage History

Every past Salesforce outage tracked by IsDown, with detection times, duration, and resolution details.

There were 2196 Salesforce outages since October 2022. The 542 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 2, 2026

April 2026: Performance Degradation

Detected Apr 2, 2026 7:24 PM EDT · Resolved Apr 2, 2026 8:31 PM EDT · Duration about 1 hour

Salesforce experienced performance degradation across multiple instances in Europe and other regions, causing login failures, data processing disruptions, certificate validation issues, intermittent access problems, and analytics workflow failures. The incident affected numerous components across ARE, CHE, DEU, FRA, and SWE environments, impacting connector jobs, CRMA recipes, and configuration updates. The service was restored after 1.1 hours by rolling back a recent change, with monitoring continuing to ensure stability.

Minor April 2, 2026

April 2026: MuleSoft feature degradation

Detected Apr 2, 2026 1:43 PM EDT · Resolved Apr 2, 2026 2:41 PM EDT · Duration about 1 hour

Salesforce experienced a MuleSoft feature degradation affecting Runtime Manager in the US region and Anypoint Monitoring, where users encountered navigation issues and applications failed to appear in the UI. The incident lasted 58 minutes, during which certain features were unavailable or performed below optimal levels. The issue was resolved after the team identified the technical trigger and performed various tests to restore normal functionality.

Minor April 1, 2026

April 2026: Tableau Feature Disruption

Detected Apr 1, 2026 10:25 PM EDT · Resolved Apr 2, 2026 4:25 AM EDT · Duration about 6 hours

Tableau Cloud experienced a 6-hour service disruption where customers could not successfully run Prep Flows, with the primary impact in the Japan region and minimal occurrences in other regions. The incident scope expanded during investigation to affect more instances than initially identified. Service was restored by applying configuration changes to impacted infrastructure components, starting with the Asia Pacific Japan instance and then rolling out the same remediation to remaining affected instances.

Minor April 1, 2026

April 2026: Feature Disruption

Detected Apr 1, 2026 7:00 PM EDT · Resolved Apr 2, 2026 6:23 PM EDT · Duration about 23 hours

Salesforce experienced a feature disruption affecting Einstein Activity Capture (EAC), where users encountered significant delays in seeing synced emails appear on record home page activity timelines. The issue was caused by a recent system change and affected hundreds of instances globally across multiple regions. Salesforce completed a rollback to restore service, but a substantial email sync backlog required up to 24 hours to fully process, with additional capacity deployed to reduce processing time.

Minor April 1, 2026

April 2026: Performance Degradation

Detected Apr 1, 2026 11:28 AM EDT · Resolved Apr 1, 2026 11:43 AM EDT · Duration 15 minutes

Salesforce experienced a performance degradation affecting component CS250 for 15 minutes. Users could access the service but encountered slow performance, timeouts, connectivity issues, and some unavailable functionality. The incident was classified as minor with intermittent impact on service performance.

Minor April 1, 2026

April 2026: Performance Degradation - Asynchronous Processing

Detected Apr 1, 2026 8:47 AM EDT · Resolved Apr 1, 2026 9:19 AM EDT · Duration 33 minutes

Salesforce experienced performance degradation on instance USA558 affecting asynchronous processing features including Web-to-Case, Web-to-Lead, Email-to-Case, and dashboard refreshes. Customers experienced delays in these services during the 33-minute incident. The Salesforce Technology team worked to isolate and resolve the performance issues.

Minor April 1, 2026

April 2026: Performance Degradation

Detected Apr 1, 2026 7:55 AM EDT · Resolved Apr 1, 2026 8:03 AM EDT · Duration 8 minutes

Salesforce experienced performance degradation affecting component NA248 for 8 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.

Minor March 31, 2026

March 2026: Feature Disruption

Detected Mar 31, 2026 7:41 PM EDT · Resolved Apr 1, 2026 6:30 PM EDT · Duration about 23 hours

Salesforce experienced a feature disruption where the unsubscribe link within the Preference Center stopped functioning correctly across multiple global instances, though one-click unsubscribe functionality remained operational. The issue was identified as being caused by a previous change to the Preference Center system. Salesforce developed and deployed a fix-forward solution that rolled back the problematic change, with deployment completed in stages during off-peak hours across all impacted regions.

Minor March 31, 2026

March 2026: Feature Degradation

Detected Mar 31, 2026 11:40 AM EDT · Resolved Mar 31, 2026 8:01 PM EDT · Duration about 8 hours

Salesforce experienced a feature degradation affecting multiple components across CS, EU, and NA instances for 8.4 hours, causing some features to be unavailable or perform suboptimally. The issue was identified as a continuation of a previous incident triggered by a recent deployment, with customers experiencing validation errors while deploying to their environments. Salesforce resolved the incident by performing rollbacks and is monitoring system health to prevent recurrence.

Minor March 30, 2026

March 2026: Feature Disruption

Detected Mar 30, 2026 6:35 PM EDT · Resolved Mar 30, 2026 7:04 PM EDT · Duration 29 minutes

Salesforce experienced a feature disruption affecting multiple instances across 20 components, where customers encountered "Fatal Error Unknown Exception" messages when attempting to perform deployments. The incident lasted 29 minutes and impacted components across CS, EU, and NA regions. The Salesforce Technology team investigated multiple paths to isolate the cause and implement a fix to restore services.