Salesforce Outage History

The Salesforce Chat and Service Cloud Voice components across North America entered a degraded state starting at Jan 31, 2025 5:34 PM UTC, with a broad set of Chat and Voice components listed as degraded. This impacted customer interactions and voice workflows across Salesforce Chat and Service Cloud Voice in North America during the incident.

The Salesforce Status page showed multiple updates as the issue progressed, with additional components moving to degraded status at 5:48 PM UTC and 5:58 PM UTC UTC. Recovery began by Jan 31, 2025 6:20 PM UTC, as many components returned to the up state, marking the end of the incident after roughly 46 minutes. The exact cause was not disclosed in the status updates.

The Salesforce Chat service across North America and several Service Cloud Voice endpoints experienced degraded performance beginning at Jan 31, 2025 5:24 PM UTC. The incident affected a wide set of USA Salesforce Chat instances and multiple Service Cloud Voice endpoints in the region, with users likely facing delays or interruptions in chat sessions and voice interactions. The degradation persisted for about 56 minutes and the impacted services began returning to normal by Jan 31, 2025 6:20 PM UTC. The outage appears regionally focused on North America, particularly USA-based chat components and voice services.

Salesforce published multiple updates to the status page during the incident. Updates were posted at Jan 31, 2025 5:24 PM UTC, Jan 31, 2025 5:34 PM UTC, Jan 31, 2025 5:48 PM UTC, Jan 31, 2025 5:58 PM UTC and Jan 31, 2025 6:20 PM UTC as the scope and restoration progressed, with the incident affecting a large number of North America - USA Salesforce Chat components and multiple Service Cloud Voice endpoints before services returned to up status.

Salesforce's North America Core Service (USA790) briefly degraded. The service moved to a degraded state at 11:24 AM UTC and was restored to normal at 11:30 AM UTC, lasting about 6 minutes. Salesforce published two status updates during the incident to communicate the temporary disruption. The impact was localized to North America, specifically the USA790 Core Service.

Salesforce Core Service in North America (USA790) experienced a brief degradation beginning at Jan 31, 2025 11:14 AM UTC and resolving by Jan 31, 2025 11:30 AM UTC, a total duration of about 16 minutes. The issue affected the North America - USA790 Core Service component and was communicated through three official status updates before service returned to normal. The impact appeared localized to this region and component, with no broader regional effects indicated.

The Salesforce Marketing Cloud Core Service experienced a regional outage beginning in Asia Pacific, with dozens of Core Service components listed as down and impacting marketing workflows in that region. Over the next several hours the issue expanded to other regions, with multiple Core Service components across North America and Europe entering degraded states and later moving through various status updates. The outage lasted about {{time:ISO}}3 hours and 30 minutes, affecting core capabilities used for campaigns, data processing, and integrations.

The outage began at 8:59 PM UTC with Asia Pacific Marketing Cloud Core Service components going down. Dozens of APAC instances reported outages, likely disrupting core Marketing Cloud functions across the region. The outage persisted for roughly 3 hours and 40 minutes before broader regional impact started to ease.

By 10:01 PM UTC, the incident had spread to other regions. The status page showed numerous Core Service components across North America, Europe, and Asia Pacific moving to warn or down states, indicating widespread degraded performance and partial outages across multiple regions.

Recovery progressed through the night, with APAC components returning to up by Jan 31, 2025 12:39 AM UTC and many regions showing improvements in the hours that followed. The status page documented multiple transitions from down or warn to up across dozens of components, signaling restoration of the core Marketing Cloud services.

Salesforce Core Service in North America experienced a brief degraded performance starting at Jan 30, 2025 3:49 PM UTC and returning to normal by Jan 30, 2025 4:05 PM UTC. The issue affected the North America - USA9402 Core Service component and caused intermittent delays for users in that region. Salesforce posted two status updates during the event, indicating a degraded state before full recovery. Impact was regional to North America with no indication of global disruption.

Salesforce experienced a brief degraded state in the North America Core Service (USA9402), with users likely seeing intermittent access issues or slower performance. The incident began at Jan 30, 2025 3:39 PM UTC and was resolved by Jan 30, 2025 4:05 PM UTC, lasting about 26 minutes. The Salesforce status page listed the affected component as Core Service, and the service issued three status updates during the incident as it transitioned from up to warn and back to up. The issue was region-specific to North America (USA9402) with no widespread impact reported.

Salesforce CloudHub 2.0 Spaces in the North America CA-Central region experienced a brief outage affecting the CA-CENTRAL-1 deployment of the CloudHub 2.0 Runtime Plane. The incident began at Jan 30, 2025 1:34 AM UTC when the CA-CENTRAL-1 runtime plane went down and was resolved by Jan 30, 2025 1:54 AM UTC after Salesforce issued two status updates. The disruption was isolated to this regional deployment, with no indication of wider impact across other regions or services. The outage lasted about 20 minutes.

Salesforce reported a brief degraded state affecting the North America - TRUST / Other Feature. The issue began at Jan 29, 2025 10:59 PM UTC and was resolved by Jan 29, 2025 11:14 PM UTC, lasting about 15 minutes. The status page then returned to normal at 23:14 UTC, indicating the service had recovered.

The incident was short and limited to the North America TRUST / Other Feature component, with Salesforce communicating the temporary degradation through status updates before returning to an all-clear state.