Salesforce outage history

Impact began at 1:54 PM UTC when Salesforce flagged MuleSoft feature degradation affecting Experience Cloud sites with guest user configurations. The issue affected a subset of MuleSoft Private Spaces across the EU and US, blocking sandbox patching and pipeline deployments while production workloads remained unaffected. By 2:09 PM UTC, approximately 42 private spaces were degraded. One impacted space recovered via a node restart by 2:49 PM UTC, but restarting did not restore all workloads, and a suspected network configuration change in a recent platform release was identified as the likely trigger. Patch work was paused to prevent further impact while a fix was investigated.

Over the following hours, a recovery method was validated and applied to remaining spaces with third-party involvement. By 10:09 PM UTC, most MuleSoft Private Spaces across EU and US were back to a healthy state and components up again, though sandbox patching and deployments could still be impacted in a few spaces. Salesforce continued to provide guidance and actions to protect Experience Cloud guest access during recovery.

An incident began at 6:10 AM UTC with a feature service disruption affecting public-facing Experience Cloud sites. Salesforce stated that threat activity targeting guest user configurations in Experience Cloud contributed to degraded functionality across multiple North America data cloud and core services. Users accessing Experience Cloud portals may have encountered intermittent access or limited service while the issue was investigated.

During the disruption, maintenance on Salesforce's email infrastructure triggered intermittent email sending issues. The status updates tracked progress: by 7:05 AM UTC the trigger was identified and restoration began, and by 7:29 AM UTC email sending appeared stable with inbound delivery functioning, though some customers may need to retry emails that failed during the disruption. By 7:34 AM UTC the impacted components were restored to up. Salesforce also published guidance on protecting Experience Cloud guest user access to help customers harden configurations.

The incident began at Aug 18, 2026 6:04 PM UTC when Salesforce flagged a performance degradation affecting public-facing Experience Cloud sites, tied to guest user configurations and impacting North America Data Cloud components USA9004S and USA9012S. Ongoing updates through 6:29 PM UTC, 7:39 PM UTC, and 8:04 PM UTC described an investigation and efforts to implement a fix, with the affected services returned to normal by 9:19 PM UTC. Salesforce published security guidance for protecting Experience Cloud guest user access and noted that, at the time, no vulnerability had been identified (details at https://www.salesforce.com/blog/protecting-your-data-essential-actions-to-secure-experience-cloud-guest-user-access/).

Public-facing Experience Cloud sites experienced degraded performance as Salesforce monitored threat activity targeting overly permissive guest user configurations. The issue was officially described as Performance Degradation, with Salesforce providing guidance on essential actions to secure Experience Cloud guest user access and noting that no vulnerability had been identified at that time. Impact began around 10:49 AM UTC and affected users attempting to access Experience Cloud sites.

Later updates described ongoing work to address Data 360 provisioning failures in sandbox environments by deploying a corrected configuration. The remediation progressed through the afternoon, and by 4:49 PM UTC a broad set of Data Cloud and CloudHub components were restored to normal across multiple regions, though sandbox provisioning issues were still being resolved as work continued. Salesforce also provided ongoing guidance via a blog post with recommended actions to secure guest access.

Impact began at 9:55 AM UTC when Data Cloud provisioning in sandbox environments started failing. Salesforce noted the disruption was linked to a recent configuration change that did not complete as intended, and ongoing updates described threat activity targeting public-facing Experience Cloud sites, including attempts to exploit overly permissive guest user configurations. The issue affected provisioning workflows in multiple regions, delaying development and testing work that relies on Data 360 in sandboxes.

An extended disruption began at Aug 17, 2026 6:09 PM UTC when Salesforce flagged a Feature Service Disruption tied to threat activity targeting public-facing Experience Cloud sites and guest user configurations. The issue affected Core Service components across regions, with guidance published to help customers protect their orgs from guest access risks. A separate issue impacting Proactive Monitoring limit alerts was identified, while other monitoring data continued to process normally, limiting alerting for a subset of customers.

Over the following hours, Salesforce implemented remediation steps including rolling restarts on affected test and production instances and staged restarts across remaining impacted instances. By 7:44 PM UTC and into the next day, actions included broader incident communications, a rollback plan for Data 360 provisioning in sandbox environments caused by a recent configuration change, and ongoing monitoring across regions. On 9:55 AM UTC Salesforce noted continued threat activity monitoring and progress, with efforts to narrow the impact to only affected instances and discontinue communications for non-impacted ones where appropriate. By 4:49 PM UTC a broad set of Data Cloud and Core Services had returned to up state across regions, with remaining components under observation and ongoing updates as needed.

An incident affecting Salesforce services began around 4:19 PM UTC with threat activity targeting public-facing Experience Cloud sites, triggering a feature service disruption. In parallel, intermittent errors affected Account Manager as Salesforce moved it to a standby environment during a maintenance window expected to take about an hour. The disruption also touched related areas including MuleSoft connectivity in Europe and Proactive Monitoring, while Data Cloud provisioning in sandbox environments faced failures linked to configuration changes. The issue impacted multiple regions and products, with service health evolving as remediation efforts progressed.

Users began reporting degraded experiences around Aug 17, 2026 3:45 PM UTC as Salesforce flagged threat activity targeting public-facing Experience Cloud sites and potential guest-user misconfigurations. The disruption primarily affected Account Manager components across multiple regions, causing intermittent errors and limiting configuration changes while the team pursued protective measures. To restore stability, Salesforce initiated maintenance to transition Account Manager to a standby environment, with traffic remaining in read-only mode and an expected duration of about one hour starting at Aug 17, 2026 4:14 PM UTC. Progress updates through Aug 17, 2026 4:34 PM UTC indicated the deployment was proceeding and ongoing mitigation steps were being taken. As the day progressed, additional maintenance and monitoring activities continued to stabilize the environment across affected pods.

The outage began for Salesforce on Aug 17, 2026 1:39 PM UTC and disrupted Experience Cloud storefronts and Commerce Cloud services, including Storefronts and Business Manager. Users reported loading failures and, in some cases, login issues, with 500 errors when trying to access storefronts and other Commerce Cloud functionality. The impact was broad, affecting several regions and tied to core components such as Storefront access, Business Manager, Account Manager, and related Core Service layers.

As the incident unfolded, Salesforce issued updates describing ongoing investigations and changes under review, including a move to a standby environment for Account Manager to stabilize traffic. A MuleSoft connectivity degradation in the EU region further complicated access for some Direct Connect customers, and maintenance activity was initiated to transition Account Manager to a standby state with read-only access during the process. The outage persisted through the evening as teams worked to identify the trigger and restore services.

By 2026-08-18T16:49:51Z most affected services had recovered, with Core Service, Account Manager, and many Data Cloud and Commerce Cloud components returning to normal operation. Some Data Cloud provisioning in sandbox environments continued to show issues, and Salesforce began rolling out a corrected configuration for Data 360 provisioning to complete the rollback and stabilization. Across the incident, communications narrowed the impact to the instances currently affected, and non-impacted instances stopped receiving ongoing updates.

A disruption affected Salesforce Commerce Cloud storefronts and Business Manager, with related Experience Cloud functionality experiencing outage and degraded access. The issue began around 1:39 PM UTC and was first observed as users in the EU region (notably POD 248) being unable to load storefronts or access Commerce Cloud admin tools, including widespread 500 errors and intermittent connectivity problems. Over the next several hours, the incident expanded to additional layers of Account Manager and related Experience Cloud services, impacting storefronts, guest-user experiences, and otherCommerce Cloud components for a broader set of customers.

Salesforce responded with guidance to protect Experience Cloud guest-user access, engaged multiple teams, and started a maintenance effort to transition Account Manager to a standby environment in order to stabilize traffic. The maintenance progressed through the late afternoon, with initial signs of recovery appearing around 4:49 PM UTC as some components came back online, and a broad recovery continued into the next day. By 4:49 PM UTC many Data Cloud and related services were back to normal in large parts of the environment, though ongoing work remained for Data 360 provisioning in sandbox environments and some alerting features. Overall, the outage affected consumer storefront access and admin workflows for an extended period, with recovery unfolding in stages across regions and services.