Salesforce Outage History

Salesforce experienced performance degradation affecting the USA288 component, causing slow performance, timeouts, and connectivity issues that made some functionality unavailable or suboptimal. Users could still access the service but encountered intermittent performance problems. The incident lasted 33 minutes while the team investigated the root cause.

Salesforce experienced performance degradation for 51 minutes, causing slow performance, timeouts, and connectivity issues while users could still access the service. Some functionality was unavailable or running below optimal performance during the incident. The issue was resolved after investigation by the service team.

Salesforce Marketing Cloud Engagement experienced a major service disruption that prevented end users from accessing the service for 32 minutes. The incident affected multiple database components (DB7140, DB758, DB7131, DB7154) and was identified and addressed by the Salesforce Technology team. The service has been restored to normal operation.

Salesforce experienced performance degradation affecting the AUS22S component for 2 hours, causing slow performance, timeouts, and connectivity issues while users could still access the service. Some functionality was unavailable or running below optimal performance during the incident. Subject matter experts actively investigated and implemented mitigation actions to resolve the issue.

Salesforce experienced a major service disruption affecting components ARE2S, ARE4S, ARE6, and ARE12, initially caused by a localized power outage at AWS infrastructure that escalated into extensive power, network, and system-level issues requiring complete data migration. The incident prevented end users from accessing Salesforce services for over 26 days while teams executed a complex three-step recovery process involving data backup, database rebuild, and service restoration. Recovery efforts included emergency data backups to alternative locations and coordination with AWS teams to restore services, with the incident ultimately requiring historic data restoration and validation before full service was restored.

Salesforce experienced an 11.7-hour performance degradation incident affecting component IND84, where users encountered extremely slow page load times, timeouts, and connectivity issues while some functionality remained unavailable or performed below optimal levels. The issue was caused by capacity contention, and an initial rollback attempt failed before engineers successfully implemented an alternative rate limit increase that allowed services to recover. Services returned to normal performance levels with continued monitoring for validation.

Salesforce experienced a 7-minute performance degradation incident where users could access the service but encountered slow performance, timeouts, and connectivity issues. Some functionality was unavailable or running below optimal performance levels. The issue was resolved after investigation.

Salesforce experienced a performance degradation affecting the Change Data Capture service on the USA920 instance, causing delays in event delivery to customers. The issue was caused by a high volume of events overwhelming the event processing system and creating a backlog, compounded by backend communication problems. The incident lasted 42.9 hours and was resolved by restarting backend services and implementing measures to prevent further backlog growth while the system processed the accumulated events.

Salesforce experienced performance degradation affecting the USA448S component for 22 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 service degradation affecting Platform Events and Change Data Capture across hundreds of global instances starting February 23, 2026 at 12:00 UTC, causing event notifications to be delayed, missing, or appear out of order. The issue was traced to recent releases that caused connection failures, prompting Salesforce to develop and test a fix before deploying it fleet-wide in a staggered rollout beginning February 25 at 10:30 UTC. The incident was resolved after 33.3 hours, with Salesforce later narrowing the scope of affected instances and removing unimpacted ones from further communications.