Salesforce Outage History

Salesforce experienced a feature disruption affecting consent-related functionality in Marketing Cloud, where customers were unable to update consent preferences, unsubscribe via Privacy Center links, or complete campaign actions that update consent status due to API call failures. The issue was caused by a recent deployment and affected multiple instances globally across regions including USA, Australia, India, Japan, Brazil, and several European countries. The incident was resolved through a deployment rollback after 23 minutes, with the team continuing to validate recovery.

Salesforce Marketing Cloud Engagement experienced a feature degradation that caused intermittent slowness or unavailability across multiple database instances, with SOAP API retrieve calls for the DataFolder object type specifically failing for customers. The incident affected a large number of database components across the platform. The service degradation was resolved after 51 minutes.

MuleSoft experienced a 57-minute disruption affecting API mocking functionality in the EU Anypoint platform, preventing customers from mocking APIs available on the Anypoint or Exchange asset platform. Salesforce deployed a targeted fix and observed signs of recovery as the deployment progressed, with some customers seeing service restoration while others continued to experience issues during the rollout. The incident was fully resolved after the deployment completed across all affected systems.

Salesforce experienced a major service disruption affecting the USA594 component that prevented end users from accessing the service. The outage lasted 16 minutes while the team investigated the issue. The disruption has been resolved, restoring normal service access for affected users.

Salesforce experienced performance degradation for 1 hour, causing general slow performance, timeouts, and connectivity issues. While users could still access the service, some functionality was unavailable or running below optimal performance. The incident was classified as minor and has been resolved.

MuleSoft experienced a feature disruption that prevented end users from accessing certain aspects of the service, with customers encountering intermittent unavailability and delays when loading the UI for AnyPoint Monitoring and Visualizer. The incident was classified as minor and lasted 43 minutes. The disruption occurred during an extended maintenance window that exceeded its planned duration.

A feature disruption in Salesforce Marketing Cloud Engagement caused end-user replies to WhatsApp messages to fail, which also resulted in related workflows failing. The issue affected multiple database instances across the platform for 2.8 hours. Salesforce resolved the problem by performing staggered restarts of the impacted instances after identifying the technical trigger.

Salesforce experienced performance degradation affecting component CS267 for 1.3 hours, causing general slow performance, timeouts, and connectivity issues. Users reported that SSO functionality was not working during the incident. The service remained accessible but with reduced functionality and suboptimal performance.

Salesforce Data Cloud experienced a feature degradation affecting multiple instances across USA, Germany, India, and Japan for 1.8 hours. Some Data Cloud features were unavailable or performed below optimal levels during this incident. The service team investigated and resolved the issue, restoring normal functionality to all affected components.

Salesforce experienced a service performance degradation lasting 34 minutes that caused general slow performance, timeouts, and connectivity issues. While users could still access the service, some functionality was unavailable or running below optimal performance levels. The incident was classified as minor and has been resolved.