Salesforce Outage History

The Salesforce outage began on Mar 24, 2025 2:09 PM UTC with Core Service components in North America entering a degraded state, and then spread to EMEA and Asia Pacific in the following days. Over a multi-day span, Salesforce issued numerous status updates showing multiple regions and components alternating between up and warn states, including Core Service, Data Cloud, and related services. The incident persisted into early April, with observed instability continuing through Apr 3, 2025 2:21 PM UTC. User reports described intermittent connectivity, slow pages, login problems, and other access issues in locations such as Atlanta, Hackney, Amsterdam, and Amsterdam, The Netherlands.

Salesforce reported widespread degraded performance affecting Core Service components across North America, EMEA, and Asia Pacific. Users experienced intermittent access, slower pages, and login anomalies during the incident. The degradation began on Mar 24, 2025 1:59 PM UTC when multiple Core Service components in North America were listed as degraded, with additional regions subsequently affected. Over the next several days, dozens of Core Service and related components, including Data Cloud and Connect & Mix services, toggled between degraded and operational states as Salesforce published regular status updates. This extended duration affected the ability of customers to access and use Salesforce applications and data across regions.

Recovery unfolded gradually, with components returning to operational status in stages. The final updates on Apr 3, 2025 4:35 AM UTC signaled broad restoration, though some services experienced intermittent issues during the transition. The incident involved a large number of components and a high volume of status updates, reflecting Salesforce's broad regional footprint and the extensive scope of the degraded service period.

Salesforce's Asia Pacific Core Service (IND102) experienced a brief degraded performance, with the status page moving from up to warn at Mar 23, 2025 8:39 PM UTC and back to up at Mar 23, 2025 10:39 PM UTC, lasting about 2 hours. The issue was confined to the Asia Pacific region and affected customers relying on the Core Service. Salesforce issued two official status updates during the incident and confirmed full recovery after the second update.

Salesforce experienced a brief degraded state in the Asia Pacific IND102 Core Service. The component transitioned from up to degraded at 8:29 PM UTC with a further status update at 8:39 PM UTC, and then returned to normal at 10:39 PM UTC. The incident affected the Asia Pacific region and lasted about 2 hours and 10 minutes. Salesforce issued three official status updates during the event, describing the degradation and recovery.

The Salesforce Asia Pacific IND102 Core Service entered a degraded state beginning at 8:24 PM UTC with follow-up status updates at 8:29 PM UTC and 8:39 PM UTC. The component returned to normal by 10:39 PM UTC. This brief partial outage affected users relying on the Asia Pacific core service, potentially impacting workflows and integrations dependent on Salesforce core functionality.

The incident lasted roughly 2 hours and 15 minutes, during which Salesforce issued four official status updates. Impact appeared limited to the Asia Pacific IND102 Core Service, with no indication of broader regional disruption.

Salesforce experienced a brief degraded performance affecting seven North America Core Service components: USA9906S, USA9914, USA9402, USA9404S, USA9904S, USA9902, and USA9918S. The issue began at Mar 23, 2025 1:54 PM UTC when the status page transitioned from up to warn and was resolved by Mar 23, 2025 2:14 PM UTC, lasting about 20 minutes. The affected components returned to normal by the second status update, with services returned to an operational state. The impact appeared limited to these North America Core Service components and did not indicate a broader global disruption.

The Salesforce North America Core Service experienced a brief degraded state affecting six components: North America - USA9402 / Core Service, North America - USA9404S / Core Service, North America - USA9406S / Core Service, North America - USA9904S / Core Service, North America - USA9902 / Core Service, and North America - USA9918S / Core Service. The incident began on Mar 23, 2025 2:59 AM UTC and was resolved by Mar 23, 2025 3:09 AM UTC, lasting about 10 minutes. Users in the North America region may have experienced intermittent access or degraded performance during this window.

Salesforce experienced a brief degraded performance affecting six Core Service components in North America (USA9402, USA9404S, USA9406S, USA9904S, USA9902, USA9918S). The issues began at 2:49 AM UTC and were restored by 3:09 AM UTC, lasting roughly 20 minutes. Users accessing Salesforce applications relying on Core Service may have experienced slower responses or intermittent errors during the window. The incident prompted three official status updates, reflecting the transition into degraded service and subsequent restoration.

Starting at Mar 21, 2025 6:24 PM UTC, Salesforce reported a degraded state affecting Data Cloud components and related services, including Email Studio, Core Service, and API Experience Hub. The issue spanned dozens of Data Cloud components across multiple regions, likely causing slower data processing, intermittent errors, and partial functionality for data workflows and integrations. The impact varied by service but was broadly felt by users relying on Data Cloud capabilities.

The incident affected Salesforce Data Cloud across multiple regions (North America, EMEA, and Asia Pacific), including related components such as API Experience Hub, Email Studio, and Core Service. Users may have experienced degraded performance, slower data processing, and intermittent access to dashboards and APIs across affected areas. The outage began on Mar 21, 2025 6:14 PM UTC as the status page reported degraded service and continued with components fluctuating between degraded and recovering states. By Mar 22, 2025 5:04 PM UTC many affected components had returned to normal operation, indicating a broad restoration of services.