Salesforce Outage History

Salesforce Core Service components across North America experienced degraded performance beginning at May 16, 2025 2:24 PM UTC. A broad set of North America Core Service instances transitioned to a degraded state, indicating regional impact on user operations relying on Salesforce core services. The incident affected a wide portion of the Core Service footprint in the region.

Salesforce Core Service in North America entered a degraded state on May 16, 2025 2:19 PM UTC, impacting a broad set of Core Service components. Users likely experienced slower performance and intermittent access to Salesforce features during the outage window. The incident lasted approximately 45 minutes.

The Salesforce Status page published four updates during the incident, noting degraded performance across Core Service components in North America. The service was restored to full operation by May 16, 2025 3:04 PM UTC.

The Salesforce Core Service layer in North America experienced degraded performance starting at May 16, 2025 2:06 PM UTC. Dozens of Core Service endpoints were affected, leading to slower responses and intermittent access for Salesforce users across the region. The impact spanned a broad portion of the Core Service tier, likely affecting a wide range of Salesforce features and integrations in North America. The outage lasted roughly 58 minutes, with the region gradually returning to normal as services recovered.

Salesforce posted multiple updates on its status page between May 16, 2025 2:06 PM UTC and May 16, 2025 3:04 PM UTC, detailing the degraded state and subsequent recovery. By May 16, 2025 3:04 PM UTC many components had returned to an up state, indicating the incident had largely concluded for the affected footprint.

Salesforce reported degraded performance across its North America Core Service components beginning at May 16, 2025 2:06 PM UTC. A broad set of Core Service components transitioned from operational to degraded, potentially impacting access to Salesforce CRM features, dashboards, APIs, and related services for users in the region. The degradation persisted for about 58 minutes, with most services returning to normal by May 16, 2025 3:04 PM UTC.

Salesforce experienced a regional outage affecting the FRA90 Core Service in the EMEA region. The outage began at 7:28 PM UTC when the FRA90 Core Service moved to a non-operational state, likely impacting access to Salesforce features for users in that region. The outage lasted approximately 2 hours and 11 minutes and was resolved by 9:39 PM UTC.

During the incident, Salesforce issued five status updates documenting the progression from degraded performance to a full outage and eventual restoration. The impact was confined to the FRA90 Core Service within the EMEA region, with other Salesforce services remaining unaffected.

Salesforce's FRA90 Core Service in the EMEA region experienced a degradation starting at 6:59 PM UTC, escalating to a regional outage by 7:28 PM UTC. Users relying on Salesforce services in Europe may have faced outages or degraded performance tied to the FRA90 Core Service. The outage persisted for about 2 hours and 11 minutes and was fully restored by 9:39 PM UTC. During the incident, Salesforce published multiple official status updates detailing the progression from degraded to outage and the subsequent recovery for the FRA90 Core Service. The issue appeared isolated to the FRA90 Core Service in the EMEA region, with no broad impact observed elsewhere.

Salesforce FRA90 Core Service in the EMEA region experienced a phased impact starting at May 15, 2025 6:49 PM UTC with degraded performance, followed by a regional outage for the FRA90 Core Service from May 15, 2025 7:28 PM UTC to May 15, 2025 9:39 PM UTC. Users in the EMEA region relying on Salesforce core functionality may have faced interruptions in CRM access, data updates, and related operations during the outage window.

Recovery was confirmed by May 15, 2025 9:39 PM UTC. Over the incident, Salesforce published seven status updates documenting the progression from degraded performance to outage and eventual restoration. The outage lasted roughly 2 hours and 11 minutes.

The Salesforce Content Builder service experienced a partial outage impacting content creation and publishing workflows across Asia Pacific and North America. The incident began at 8:04 AM UTC and was largely resolved by 3:49 PM UTC, with dozens of Content Builder blocks transitioning from degraded to operational as recovery progressed.

Salesforce posted multiple status updates during the incident. In total, the provider released 6 updates describing the recovery progress, and by mid-afternoon most regions had returned to normal across the majority of Content Builder components, while a subset in B2C Core POD194 remained degraded for part of the window before full recovery.

Salesforce Content Builder experienced a broad degradation affecting a large set of backends in Asia Pacific and North America beginning at May 15, 2025 7:59 AM UTC. Users attempting to publish, retrieve, or manage Content Builder assets could encounter errors or delays as the backend services operated in a degraded state. The outage impacted dozens of Content Builder components across the two regions, leading to intermittent issues for content workflows. The outage persisted for several hours with most components returning to normal progress starting mid‑afternoon, and the final affected POD194/B2C Core component restored by May 15, 2025 3:49 PM UTC.

The Salesforce Status Page published multiple updates during the incident, documenting the progression from degraded to restored as components in Asia Pacific and North America moved from warn to up. By around 1:16 PM UTC the majority of Content Builder backends had recovered, and ongoing updates reflected the restoration of remaining components. The issue concluded with full restoration for the POD194/B2C Core service in North America by May 15, 2025 3:49 PM UTC.

Salesforce Data Cloud components across North America and Europe, the Middle East, and Africa (EMEA) experienced degraded performance, with dozens of Data Cloud components showing warning events. Users relying on Data Cloud for data ingestion, processing, and analytics may have faced slower responses or intermittent access during the incident. The disruption affected multiple regional components, including regions in North America and SWE18 in EMEA.