Salesforce Outage History

Salesforce faced a multi-region disruption that disrupted the B2B Order Capture interface (version 26.2), causing issues with records in Business Manager and out-of-stock errors. The outage affected multiple Cart Service and B2C Core components across EMEA, Asia Pacific, and North America, impacting checkout and related workflows for customers. The outage began at Feb 20, 2026 8:14 PM UTC and persisted as services operated with degraded performance across regions.

Status updates described ongoing investigation, with initial root-cause tracing to a change deployed on February 9, 2026. Salesforce discussed a fix-forward approach and began developing a patch. The fix was validated on POD311 on Feb 21, 2026 3:49 AM UTC UTC and deployment to remaining PODS followed. By Feb 21, 2026 1:24 PM UTC, the majority of Cart Service and B2C Core pods were restored and services returned to normal operating levels. During the incident some connected services were temporarily impacted or disabled (for example, Drift remained offline as part of remediation), with Salesforce providing guidance at help.salesforce.com.

The Salesforce Marketing Cloud Journey Builder experienced a feature degradation that impacted the configuration page and Journey Builder API endpoints across dozens of EMEA components. Users attempting to configure journeys or call Journey Builder APIs may have faced intermittent access or failures during the incident. Salesforce labeled the issue Marketing Cloud Feature Degradation and noted security remediation steps were in progress, including re-enabling most Salesloft integrations while keeping the Drift app disabled for now.

Timeline and recovery: The incident began on 4:54 PM UTC with the status moving to warning, followed by updates at 4:59 PM UTC and 5:04 PM UTC. By 5:29 PM UTC, a large set of Journey Builder components in the EMEA region had returned to the up state. The outage lasted roughly 35 minutes, and Salesforce directed customers to follow their help article for ongoing guidance.

An outage on Salesforce's Heroku platform in North America (Virginia) disrupted the Data and Apps components, causing database connectivity issues and preventing access to some applications. The incident began at 1:49 AM UTC and was resolved by 3:04 AM UTC, lasting about 1 hour and 15 minutes and primarily affecting users in North America. The outage impacted two components: North America - Heroku Virginia / Data and North America - Heroku Virginia / Apps. The service issued five official status updates during the incident as the team investigated and worked to restore functionality.

Salesforce experienced a service disruption beginning Feb 17, 2026 5:49 AM UTC affecting 13 North America core service instances (USA9402, USA9002, USA9006S, USA9010S, USA9012S, USA9014, USA9016S, USA9018S, USA9020, USA9022S, USA9026, USA9028S, USA9008). Users could encounter login errors, slow page loads, and intermittent unavailability across affected services.

Six official updates were posted during the incident as engineers investigated and worked to restore service. The root cause was traced to a caching service connectivity issue triggered by a recent configuration update. Restart procedures and partial rollback of recent application changes were performed on several instances, with full restoration achieved by Feb 17, 2026 8:54 AM UTC. The outage lasted approximately 3 hours and 5 minutes.

An outage in Salesforce’s Agentforce feature disrupted AI functionality in the EMEA region, with users reporting failures loading custom prompts in the contact center. Standard prompts were not affected. Dozens of Agentforce components across GBR locales were listed as impacted. The outage began at 1:29 PM UTC and was resolved by 2:29 PM UTC.

Salesforce issued four status updates during the incident, noting a feature disruption and that a recent release could be a trigger. A rollback was attempted on a test instance to verify a fix, and, if successful, would be rolled back across all impacted instances. By the time the issue was resolved, affected components were brought back up, restoring AI prompts and related functionality.

The North America - NA248 Core Service experienced a brief performance degradation starting at 11:05 AM UTC and was resolved by 11:14 AM UTC. The incident affected user workflows and integrations within that region and included two official status updates. The issue appeared regional to North America NA248 Core Service, with no broader impact reported.

As part of ongoing security incident remediation, Salesforce re-enabled most integrations with Salesloft technologies, while the Drift app remained disabled until further notice.

Salesforce’s North America core service (NA253) experienced a brief performance degradation beginning at 7:24 AM UTC. During the incident, Salesforce re-enabled most integrations with Salesloft, but the Drift app remained disabled as part of ongoing security remediation. Users relying on these integrations may have seen intermittent delays or incomplete automation during the window. The core service returned to normal by 8:54 AM UTC, with the outage lasting about 1 hour 30 minutes. The Salesforce status page issued two updates during the incident, noting that Drift would remain disabled until further notice. Impact was localized to the North America core service NA253, with no user reports recorded during the incident.

Salesforce's MuleSoft Anypoint Runtime Manager UI in the North America GOV region experienced a brief outage, with the UI displaying an empty screen and an error message preventing users from viewing their applications. The incident began at Feb 11, 2026 2:39 PM UTC and was resolved by Feb 11, 2026 3:44 PM UTC, lasting about 1 hour and 5 minutes. The issue was traced to a deployment and affected the North America GOV / Runtime Manager component. The provider issued 2 official updates during the incident.

Salesforce reported a MuleSoft feature disruption affecting the North America - Anypoint Management Center - GOV / Runtime Manager. The issue briefly impacted integrations, with the Drift app remaining disabled as part of the ongoing security incident response. Salesforce has re-enabled integrations with Salesloft technologies, but Drift will stay disabled until further notice during remediation.

The incident was short, with two official updates from Salesforce. The outage began on 2:24 PM UTC and was resolved by 2:34 PM UTC, lasting roughly 10 minutes. Customers relying on the affected GOV/RM workflows may have experienced intermittent integration issues during the window.

Salesforce's Asia Pacific AUS18S core service experienced a brief performance degradation beginning at 11:35 AM UTC and resolving at 11:49 AM UTC, lasting about 14 minutes. The impact was regional to APAC, with other Salesforce services functioning normally. During the incident, Salesforce re-enabled integrations with Salesloft technologies, while the Drift app remained disabled as part of ongoing security remediation following a security incident.