Salesforce Outage History

A Salesforce maintenance window overran and caused a service disruption lasting 2.4 hours, preventing end users from accessing the service. Two instances were affected (AP52 and AP62), with AP52 being restored first and AP62 requiring additional recovery work. The incident was resolved by restoring service access to the affected instances.

Salesforce experienced a 3.5-hour performance degradation affecting component NA245, where users encountered elevated message queue latency, "out of heap memory" errors, failed data pipeline jobs, and issues with asynchronous processing including bulk jobs and Apex features. The incident was resolved through service restarts, with monitoring showing errors ceasing and jobs beginning to succeed again.

Salesforce experienced a feature degradation lasting 19.2 hours that affected DevOps pipeline automations across 9 instances in multiple regions (Germany, USA, Australia, and Sweden), causing "Apex test failure" errors when customers attempted to perform deployments. The incident was triggered by a recent release, and after an unsuccessful rollback attempt, engineering teams developed an emergency code fix that was validated through testing and deployed in a staggered manner across all impacted instances. The fix deployment took several hours to complete to minimize user impact during the resolution process.

Salesforce experienced a major service disruption on April 16, 2026, starting at 04:20 UTC that prevented customers from logging into the platform or accessing any services on the CS342 sandbox instance. The incident lasted approximately 1 hour with the team investigating multiple resolution paths. The service was classified as a major outage affecting all user access to the Salesforce platform during the disruption period.

Salesforce experienced a feature degradation affecting Commerce Cloud customers in the North America region across 23 PODs, where users were unable to modify Content Delivery Network (CDN) configurations via Business Manager due to rate-limiting issues with a third-party backend service provider. Storefront operations and checkout functionality remained fully operational throughout the incident. The issue was resolved after 59 minutes with Salesforce teams working directly with the vendor to restore full functionality.

Salesforce experienced a feature degradation affecting Industry Cloud customers' Document Generator and PDF Generator functionality, causing significant slowness and delays in retrieving document previews. The incident impacted components GBR100, GBR112, GBR122, and GBR70, with requests experiencing intermittent delays rather than complete failures. The trigger was identified and a fix was implemented, with the resolution process taking several hours to complete over a 16-hour duration.

Salesforce experienced performance degradation for 10.3 hours affecting components AP43-AP50 and CS294, CS310, CS314, CS315. Users encountered slower response times when creating or updating records, impacting activities like case creation, order processing, and automated workflows, along with general slow performance, timeouts, and connectivity issues. The service team actively worked to restore normal performance levels.

Tableau Cloud experienced a 9.5-hour performance degradation that prevented customers from loading embedded Tableau views within Salesforce Lightning Web components, displaying "The connection was refused" errors. The issue was caused by a recent deployment in the US West 2 region that handles SSO/Authentication for embedded views. Tableau engineers resolved the incident by rolling back to a previously stable version, with service recovery observed at 09:33 UTC.

Salesforce experienced a service disruption affecting Data 360 functionality across multiple instances starting April 13 at 20:58 UTC, lasting 3.7 hours. The incident impacted Data Streams, Profile Engine, Actions Service, and Scheduler Service features, preventing customers from properly navigating or utilizing these Data 360 components. Salesforce resolved the issue by identifying the trigger and increasing system capacity, with services returning to healthy status.

Salesforce experienced performance degradation affecting the IND100 component for 39 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.