Salesforce outage history

Salesforce reported a feature performance degradation affecting Agentforce session scoring and tagging for a subset of customers. The issue centered on session processing in North America Agentforce environments, leading to delays or failures in scoring and tagging workflows. The incident began at 8:24 PM UTC as engineering teams investigated and narrowed the cause to processing failures during sessions.

By 10:44 PM UTC, a potential fix had been identified and prepared for deployment to affected environments. After the change, teams monitored session tagging performance to confirm recovery, and by 11:25 PM UTC the North America Agentforce components had returned to normal operation. Salesforce continued to monitor for any residual issues.

A security-related disruption affected Salesforce Experience Cloud sites and Commerce Cloud checkout, causing credit card transactions to fail for customers. The incident began with threat activity targeting public-facing Experience Cloud guest-user configurations, and impact on checkout processing started around 4:55 AM UTC. Salesforce described the event as a feature service disruption and initiated restarts of affected applications to restore transaction processing, while providing customers with guidance on how to secure Experience Cloud guest-user access.

The Salesforce Agentforce service began experiencing performance degradation at 7:09 PM UTC, with slower responses and intermittent errors affecting workflows that rely on Agentforce. The issue appeared across multiple regions and environments, reducing productivity for teams that depend on Salesforce automation and data processing. As the incident expanded, merchants relying on Commerce Cloud checkout also faced disruption as part of a broader service impact.

An global disruption affected Salesforce Revenue Cloud and Experience Cloud, causing issues with adding new products, saving quotes, and checkout for some customers. The impact spanned multiple regions (NA, EMEA, APAC) and touched core services and B2B2C commerce components, with Experience Cloud guest user configurations identified as a factor. Users reported degraded checkout and quoting experiences, while some could view existing quotes but could not modify or complete purchases. Salesforce began communicating guidance to protect Experience Cloud guest access as the issue unfolded, and a security-focused blog post was shared to help customers mitigate risk (link: https://www.salesforce.com/blog/protecting-your-data-essential-actions-to-secure-experience-cloud-guest-user-access/).

Salesforce experienced a service disruption affecting public-facing Experience Cloud sites due to threat activity targeting guest user configurations. Impact began at 11:34 AM UTC, with the North America - AWS US / Platform component moving to a down state and the North America - USA1000 Core Service following, leaving guest users with access issues on Experience Cloud pages. Salesforce provided guidance to customers on protective actions via a dedicated blog post to help secure Experience Cloud guest access.

The incident began at Sep 5, 2026 3:59 AM UTC with performance degradation tied to threat activity targeting public-facing Experience Cloud guest-user configurations. Public Experience Cloud sites, including core North America storefronts (North America - USA1000 / Core Service), experienced slower responses and intermittent access issues as the situation evolved toward a broader disruption. Salesforce actively monitored the activity and provided guidance to protect customer orgs while investigations continued.

Salesforce issued updates as the issue was isolated and persisted through the day, moving from a degraded state to a full disruption for several components in North America. A fix for a related B2B Commerce visibility problem was verified and began deploying by Sep 6, 2026 2:29 PM UTC, with all environments expected to receive the update by Sep 7, 2026 12:00 AM UTC. By 7:14 PM UTC most B2B Commerce instances were back online, marking the path toward full recovery.

Users of Salesforce Experience Cloud experienced site disruptions beginning around 11:34 AM UTC as threat activity targeted public-facing Experience Cloud sites, exploiting overly permissive guest-user configurations. The impact affected guest access to Experience Cloud pages and disrupted B2B Commerce environments across multiple regions including North America, Europe, and Asia Pacific. Salesforce isolated the issue and continued monitoring, noting that no vulnerability had been identified at that time and providing guidance to protect guest-user access. A fix was verified and deployment began at 2:29 PM UTC, with updates indicating rollout across impacted environments in the following days. By 7:14 PM UTC a broad set of B2B Commerce instances had recovered and most impacted services were back online.

Salesforce experienced a multi-faceted disruption starting at 11:34 AM UTC tied to threat activity affecting public Experience Cloud sites and guest-user configurations. The incident also included a regional platform outage on the North America - AWS US/Platform and broader degraded performance across multiple regions, impacting users accessing Experience Cloud sites. At the same time, outbound emails sent from Salesforce through a third-party provider were delayed or failed due to rate-limiting by the mail provider, with recipients reporting delivery challenges.

Salesforce reported a service disruption affecting Experience Cloud sites after threat activity targeted guest user configurations. The issue prompted isolation of the changes and a rollback, with impact first observed at 11:34 AM UTC on the North America - AWS US platform. By 11:49 AM UTC, core services for several instances began to recover as part of the rollback, and Salesforce issued guidance and security updates noting that no vulnerability had been identified.

Over the following hours, related issues emerged, including outbound email delays caused by rate limits from a third-party provider (the issue was resolved by 4:35 PM UTC), and a coupon code visibility problem with the B2B Commerce coupon component. Salesforce planned a fix for the coupon visibility issue in the September 5 release window (18:00 UTC, 6:00 PM UTC). By 7:14 PM UTC, most impacted Core Service and B2B Commerce instances had been restored and the fix was being rolled out across remaining instances, with outbound emails retried for up to 24 hours where necessary.

Storefront Sand or Business Manager access was unavailable starting at 9:34 AM UTC after a deployment restart removed a required network entry, preventing impacted services from reconnecting to application servers. The outage affected Storefront and Business Manager across multiple Core Service components and regions, leading to widespread disruption for customers trying to use storefront and admin capabilities.

Status updates showed targeted configuration fixes were applied but did not immediately restore service. By 12:34 PM UTC a misconfiguration was identified and connectivity was restored on some instances. As the issue persisted, Salesforce pursued a targeted rollback of the recent release; by 5:50 PM UTC the rollback had been completed for production and sandbox environments, restoring access to OmniScripts and FlexCards, though some browser-based workflows remained affected on certain browsers like Chrome. The incident then broadened into ancillary service impacts, including downstream workloads and data services, before stabilization.

Over the following days, Salesforce managed related challenges such as outbound email delays caused by a third-party rate-limiter and ongoing feature degradations in Data Cloud and B2B Commerce components. The third-party email issue was addressed and delivery was restored around 6:20 PM UTC, while a fix-forward and staggered rollback continued for affected Data Cloud and Commerce instances. By 7:14 PM UTC most core services had recovered across regions, with ongoing validation and phased redeployments continuing to complete.