Salesforce Outage History

From Feb 9, 2025 10:19 AM UTC Salesforce Core Service components across North America, Europe (EMEA), and Asia Pacific transitioned to degraded state, causing widespread performance issues for Salesforce users. The incident affected dozens of Core Service components, impacting login, data access, integrations, and routine CRM workflows as users experienced slower responses and intermittent errors across multiple regions.

Salesforce provided regular status updates documenting the progression of the incident, noting multiple components moving from degraded to restored. The recovery progressed in waves, with a large portion of services returning to normal by around Feb 10, 2025 8:34 PM UTC and the remainder steadily recovering into the evening of that day. The incident lasted roughly 34 hours before broad restoration, with ongoing post-incident validation of services for a number of components.

Salesforce experienced brief degraded performance in the EMEA Core Service (DEU132). The issue began at Feb 9, 2025 12:29 AM UTC and was resolved by Feb 9, 2025 1:29 AM UTC, for a duration of about one hour. The impact was localized to the EMEA region and did not indicate a global outage. The provider issued 2 official status updates during the incident. There were no notable user reports observed.

An isolated degradation affected Salesforce's EMEA Core Service DEU132. The outage began at 12:21 AM UTC and was resolved by 1:29 AM UTC. The provider issued 3 official updates during the incident, and the impact was limited to the EMEA region.

The issue was contained to the DEU132 Core Service in the EMEA region, with users potentially experiencing slower performance or intermittent access during the event.

Salesforce's EMEA Core Service (DEU132) experienced a brief degraded period, with the Core Service listed as degraded beginning at 12:19 AM UTC and returning to normal at 1:29 AM UTC, lasting about 1 hour and 10 minutes. The impact was limited to the EMEA region, affecting only the DEU132 Core Service.

The provider issued four status updates during the incident to communicate the degraded state and restoration.

Salesforce reported a brief degraded access impacting the North America - Anypoint Management Center - CA / Access Management component. The incident began at 4:29 PM UTC and was resolved by 7:19 PM UTC, lasting approximately 2 hours and 50 minutes. The Salesforce status page issued 2 updates during the event as engineers worked to restore access. The impact was confined to the Access Management function within the North America Anypoint Management Center.

Salesforce experienced a global outage of its Core Service beginning at Feb 7, 2025 10:20 AM UTC, impacting core CRM access, APIs, and dashboards across Asia Pacific, Europe, and North America. Users reported difficulties signing in, failed API calls, and dashboards not loading as multiple Core Service components entered degraded or down states. The outage lasted several hours, with services gradually moving toward restoration across regions and ultimately recovering over time. The disruption affected a broad set of customers and multiple Salesforce regions.

Starting at 10:09 AM UTC, Salesforce Core Service across Asia Pacific, Europe, and North America entered a degraded state, with widespread outages and degraded performance affecting critical workflows. The disruption lasted about 5 hours and 40 minutes, with many regional Core Service components alternating between degraded and unavailable. Users across multiple regions experienced interruptions until recovery progressed in the afternoon.

Salesforce documented the incident via its status page, posting a series of updates that described the spread of the outage and the subsequent restoration efforts. The updates tracked transitions from warning to down and then back to up as engineers worked to restore services. By around 3:37 PM UTC, many regions had returned to normal, with final components recovered by 3:49 PM UTC, and ongoing monitoring to ensure stability.

An outage began at Feb 5, 2025 7:54 PM UTC and impacted Salesforce Marketing Cloud Core Service across North America, Europe (EMEA), and Asia Pacific. Dozens of core databases and components within Marketing Cloud Core Service became unavailable, affecting campaign execution, data processing, and related features for customers in these regions.

Over the course of the incident, multiple components were listed as down or degraded and Salesforce issued several status updates as the situation evolved. The outage lasted approximately 4 hours and 10 minutes and was resolved by Feb 6, 2025 12:04 AM UTC as services returned to an up state across impacted regions.

Geographic spread was regional rather than global, with activity tracked across North America, EMEA, and Asia Pacific. The incident illustrates the breadth of impact on the Marketing Cloud Core Service and related databases during the event.

The outage began on Feb 5, 2025 7:44 PM UTC when Salesforce Marketing Cloud Core Service components across multiple regions went offline, including EMEA, North America, and Asia Pacific. The disruption affected the core Marketing Cloud databases and services, likely impacting campaign creation, data processing, and related features for users across these regions. Over the course of the incident, several components moved to degraded or down states before a broad outage was declared.

Salesforce documented 9 status updates during the incident as recovery efforts progressed. The incident saw some regional degradation, with Asia Pacific AUS80S Core Service and North America TRUST components transitioning through degraded (warn) states before restoration. By Feb 6, 2025 12:04 AM UTC a large majority of core service components were back online across EMEA, North America, and Asia Pacific, marking the end of the outage. The overall duration was approximately 4 hours and 20 minutes.

The outage began at 2:34 AM UTC and was resolved by 3:24 AM UTC, lasting about 50 minutes. Salesforce's North America CS271 Core Service briefly went offline, affecting users relying on that core component. The incident moved from up to down and back to up, with Salesforce publishing two status updates describing the disruption and its restoration.