Salesforce Outage History

Salesforce experienced a feature degradation lasting 8.5 hours that affected search functionality on components JPN134, JPN136, JPN144, and JPN140, causing delays in search results and slower response times due to a Solr service issue. The problem was traced to a faulty pod that became stuck in the system, incorrectly reporting as healthy and preventing traffic failover to new components. The issue was resolved by engaging the cloud provider to forcefully terminate the problematic pod and restore normal operations.

Salesforce Marketing Cloud Engagement experienced a degradation affecting hundreds of database components, causing intermittent slowness, unavailability, login failures, failed email/journey sends, and SQL database operation errors. The incident lasted 5.2 hours and was resolved through coordinated parallel reboots and service restarts across the impacted database infrastructure, with services being restored in phases as each database subset was successfully restarted.

Salesforce experienced a performance degradation affecting the IND26S component for 5 minutes. Users could access the service but encountered slow performance, timeouts, connectivity issues, and some unavailable functionality. The incident was classified as minor and the team investigated the issue with updates promised within 30 minutes.

Salesforce experienced a feature disruption affecting multiple sandbox instances where users could not view existing custom prompt templates or create new ones, with only standard templates visible and errors occurring during custom template creation attempts. The incident affected 54 components and lasted 2.8 hours, with production instances remaining unaffected. The issue was resolved by rolling back a recent deployment change, first on a test instance and then across all remaining impacted sandbox instances.

An unplanned upgrade was accidentally triggered on MuleSoft's Anypoint Private Spaces during infrastructure patch preparation, affecting a subset of environments with runtime restarts. The incident occurred outside the scheduled maintenance window when an upgrade process was unintentionally started and then halted. MuleSoft's engineering team monitored the affected environments and reported no observed service degradation, though they acknowledged the disruption caused by the unscheduled maintenance.

Salesforce experienced performance degradation affecting the FRA32 component for 38 minutes. Users could access the service but encountered slow performance, timeouts, and connectivity issues, with some functionality unavailable or running suboptimally. The incident was classified as minor and has been resolved.

Salesforce experienced a feature degradation lasting 3.4 hours that prevented users from refreshing their analytics dashboards across multiple US instances. The issue was isolated to the environment where recipe jobs run, affecting dozens of Salesforce instances including USA1, USA220, USA312, and many others. The service was restored after investigation and remediation efforts by the Salesforce team.

MuleSoft Anypoint Platform experienced a performance degradation affecting users in the US region, causing login issues, slow performance, timeouts, and connectivity problems. The incident was traced to database tier contention issues, which were resolved through necessary corrective actions. The service was restored to normal operations after 24 minutes with positive initial outcomes confirmed through health checks and performance monitoring.

Salesforce experienced performance degradation in Commerce Cloud development environments on POD217 and POD297, causing significant slowness in Business Manager with pages taking several minutes to load, incorrect rendering, timeouts, and session errors that delayed development activities like reviewing promotions and content. The incident lasted 6.7 hours and was resolved through a temporary fix that restored normal performance, followed by configuration changes applied as a permanent solution across the remaining instances with brief 5-minute downtimes during the fix deployment.

Salesforce experienced performance degradation affecting Commerce Cloud development environments on PODs 217 and 297, causing significant slowness in Business Manager with pages taking several minutes to load, incorrect rendering, and session timeouts that delayed development activities like reviewing promotions and content. The incident lasted 54 minutes and was resolved with a temporary fix that restored normal performance, while production environments remained unaffected throughout the incident.