Salesforce Outage History

The Salesforce North America Core Service (NA241) briefly degraded, impacting users in the North America region. The incident began at May 20, 2025 3:44 PM UTC when the Core Service moved to a degraded state and was resolved by May 20, 2025 4:23 PM UTC, lasting about 39 minutes. During the event, customers could have experienced intermittent performance issues or limited access to features tied to the Core Service. The issue affected the North America Core Service component as listed on the Salesforce status page.

The Salesforce status page posted two updates during the incident, with the service returning to normal at May 20, 2025 4:23 PM UTC. Monitoring indicates the issue has been resolved, and no extended impact was reported.

Salesforce's North America Core Service (NA241) experienced a brief degraded performance starting at 3:34 PM UTC and returning to normal by 4:23 PM UTC, a duration of about 49 minutes. The issue appeared localized to the North America NA241 Core Service. During the incident, Salesforce posted multiple status updates and then restored normal service as the issue was resolved.

Salesforce reported a regional outage impacting the B2C Core service across six regional endpoints: Asia Pacific ODS-AP01, North America ODS-US01/US03/US02/US04, and Europe ODS-EU01. This outage left Salesforce B2C Core features unavailable or degraded for users in these regions. The incident began on May 20, 2025 10:39 AM UTC and was resolved by May 20, 2025 3:14 PM UTC, lasting approximately 4 hours and 35 minutes. The provider issued two official status updates during the incident, first documenting the regional impact and ongoing degradation, then confirming restoration across all listed components.

Salesforce experienced degraded performance in North America affecting the USA9002 Core Service and Search components. The incident began at 5:14 AM UTC and lasted about 2 hours and 10 minutes, during which users in the affected region could have encountered slower responses and partial operational issues in core functionality and search.

Two official status updates were issued during the incident, confirming the degraded state and subsequent restoration. The affected components were North America - USA9002 Core Service and North America - USA9002 Search, which returned to normal operation by 7:24 AM UTC.

Salesforce experienced a brief degraded performance affecting 2 components: North America - USA9002 Core Service and North America - USA9002 Search. Users in North America may have encountered slower responses or intermittent access to Salesforce features during the incident. The issue appeared localized to these components and did not indicate a global outage. The outage began at 5:04 AM UTC and was resolved by 7:24 AM UTC, lasting about 2 hours and 20 minutes.

During the incident, Salesforce issued 3 status updates describing the degraded service and subsequent recovery, with services returning to normal after the final update.

An outage began at 6:44 PM UTC when Salesforce CloudHub 2.0 Applications in US-EAST-2 moved to down, marking the start of a broader disruption to Salesforce Commerce Cloud services. The issue expanded to Asia Pacific, where Service Cloud Messaging Channels went down starting at 8:24 PM UTC, affecting messaging delivery and storefront operations. The US-East-2 outage lasted about 7 hours and 55 minutes, with AP messaging channels degraded for several hours and showing partial stabilization by 9:14 PM UTC. During the incident, Salesforce posted multiple updates across NA, EMEA, and AP SLAS services, with components moving through warn and down states before gradual recovery. The US-East-2 recovery occurred by 1:39 AM UTC and AP channels remained degraded beyond that point.

The outage began on 6:44 PM UTC when CloudHub 2.0 Applications in US-East-2 went down, followed by widespread disruptions to Service Cloud Messaging Channels across Asia Pacific, including multiple JP channels. North America Commerce Cloud SLAS services showed degraded status earlier in the incident. The disruption caused outages and degraded messaging delivery for customers relying on Salesforce CloudHub and related Cloud Messaging components. The impact was regional, affecting North America and Asia Pacific rather than global.

From May 16, 2025 5:19 PM UTC, Salesforce began listing degraded performance affecting a large portion of Agentforce across North America and related Core Service components. Over the next hours and days, the outage expanded to Canada, Brazil, and parts of Europe as dozens of Agentforce nodes and Core Service instances entered degraded status. Users experienced intermittent access and slowed workflows across multiple Salesforce capabilities. The incident persisted for about two days, with waves of recovery and ongoing updates to the status page. By May 18, 2025 8:14 PM UTC many components were reported as up again, though some services continued to show intermittent issues during the rollout.

Salesforce experienced widespread degraded performance across its services starting at May 16, 2025 5:09 PM UTC as multiple Agentforce and Core Service components entered degraded states across North America, Canada, Brazil, and Europe. End users likely encountered slower access and partial service interruptions across Salesforce apps during the incident, with many features impacted while Salesforce issued ongoing updates to the status page.

Salesforce Core Service components across North America experienced degraded performance for about 30 minutes. The event began at 2:34 PM UTC and was resolved by 3:04 PM UTC. The Salesforce status page listed those North America Core Service components as degraded (warn) during the incident, impacting access to CRM data and integrations for some users in the region. The provider issued two status updates during the incident, after which the affected components returned to normal.