Salesforce Outage History

The SPIFF-APP-GCP / Spiff component in North America briefly experienced an outage, causing a temporary disruption for users relying on the Spiff integration within Salesforce. The outage began at 7:49 PM UTC and was resolved by 8:19 PM UTC, lasting about 30 minutes. The impact was limited to this specific Spiff component in the North America region, with other Salesforce services remaining available.

The Salesforce status page documented the incident with two official updates: an initial note that the Spiff component was down, followed by a later update confirming restoration to normal. The incident was localized to the North America Spiff component and there was no indication of broader regional impact.

The Salesforce SPIFF-APP-GCP / Spiff integration in North America experienced a brief outage, disrupting Spiff-related functionality. The incident began at 7:44 PM UTC and was resolved by 8:19 PM UTC, lasting about 35 minutes. The outage affected the Spiff component in the North America region.

Salesforce's status page logged the downtime and subsequent restoration as the incident progressed, with no additional regional impact indicated beyond North America. The event appears localized to the Spiff integration and did not show signs of a broader Salesforce-wide disruption.

An outage impacted Salesforce's SPIFF-APP-GCP / Spiff component in North America. The issue began at 7:40 PM UTC and the service was restored by 8:19 PM UTC, lasting about 39 minutes. The incident affected the Spiff integration within the region, potentially disrupting workflows that rely on that component. Salesforce issued multiple status updates during the event to communicate the problem and its resolution.

Geographically, the impact was focused on North America, with no broader regional alerts indicated. The status page shows a sequence of down states before the component came back online, marking the incident as a brief disruption rather than a prolonged outage.

Salesforce reported a regional outage of its Core Service beginning at Jun 11, 2025 11:09 PM UTC, affecting a broad set of Core Service components across Europe, the Middle East, and Africa. Users in affected regions experienced outages or degraded performance impacting core features such as login, data access, and dashboards. The incident involved multiple EU and EMEA data centers (for example FRA12S, EU53, EU49, EU51, EU55, and DEU122) and prompted Salesforce to publish a series of updates as the situation evolved.

As the incident progressed into Jun 12, 2025 1:27 AM UTC, components in EMEA fluctuated between degraded and restored states, with several EU components recovering and others stabilizing later. North America began to see issues later in the window, with NA components moving to degraded or warned status around Jun 12, 2025 11:31 AM UTC and gradually returning to normal by Jun 12, 2025 12:34 PM UTC. The incident thus featured a phased recovery across regions with ongoing monitoring.

Duration: from Jun 11, 2025 11:09 PM UTC to Jun 12, 2025 12:34 PM UTC, roughly 13 hours and 25 minutes. The event also spurred user reports from customers in the United Kingdom (e.g., London and Manchester), which helped corroborate the timing. Salesforce provided numerous updates throughout the incident and announced restoration across the affected Core Service components as regions recovered.

Salesforce reported a multi-region outage in its Core Service that began at Jun 11, 2025 10:59 PM UTC, first impacting Europe (EMEA) and later spreading to North America. The disruption prevented access to core Salesforce features for many customers, with user reports from London and Manchester indicating connectivity and functionality issues. The incident persisted for about 13 hours and 35 minutes before recovery.

The incident prompted a long sequence of official updates—37 status changes—tracking the evolution of the Core Service across affected regions. Over the course of the outage, multiple components were degraded or unavailable before progressively returning to service. By Jun 12, 2025 12:34 PM UTC most affected components were restored and Salesforce indicated recovery across EMEA and North America. The geographic impact spanned both regions, reflecting a broad, multi-regional disruption affecting business-critical workflows.

An extended outage affected Salesforce Core Service across Europe (EMEA), beginning at 10:54 PM UTC. The disruption took down numerous Core Service components across regions such as EU49, EU53, EU51, EU55, FRA12S, DEU122 and related core services (CS332, CS328, CS333, CS331, CS329), leading to degraded access to Salesforce features reliant on the core service and impacting day-to-day operations in affected areas. The impact was most pronounced in European regions, where multiple core service components were listed as down for several hours. The outage lasted from 10:54 PM UTC to 12:34 PM UTC (roughly 14 hours 40 minutes).

Salesforce's Core Service experienced degraded performance across multiple regions, including North America, Europe (EMEA), and Asia Pacific. Users may have faced slower response times and intermittent access to Salesforce apps and services, affecting core functionality across dozens of regional Core Service components. The issue began at Jun 11, 2025 1:04 PM UTC and was resolved by Jun 11, 2025 3:04 PM UTC, lasting about 2 hours. The Salesforce status page posted 2 official updates during the incident, noting the degradation and subsequent restoration.

The disruption was global in scope, affecting many regional endpoints before service returned to normal.

Salesforce Core Service experienced a global degradation beginning at Jun 11, 2025 12:54 PM UTC, affecting Core Service components across multiple regions and leading to degraded performance and intermittent access to Salesforce features that rely on core services. The issue affected users across multiple regions with core components listed as degraded, potentially slowing operations across Salesforce products.

The incident progressed with official status updates, first moving from up to degraded at Jun 11, 2025 12:54 PM UTC and reaffirmed at Jun 11, 2025 1:04 PM UTC. The outage lasted approximately 2 hours and 10 minutes and was resolved when core services returned to normal by Jun 11, 2025 3:04 PM UTC. Salesforce published 3 status updates during the incident detailing the degradation and recovery.

Salesforce experienced a global outage starting at Jun 10, 2025 2:49 AM UTC that disrupted core cloud services including Sales Cloud, Marketing Cloud, and related CRM workflows across multiple regions. Users reported difficulties loading Salesforce pages and timeouts, with CPQ and document-generation functionality also affected. The incident impacted a broad set of components across North America, Europe (EMEA), and Asia Pacific, resulting in widespread disruption to sales, marketing, and CRM operations.

Status updates from Salesforce described a progression from outage to degraded performance and partial recovery, as components moved through down, warn, and up states as services stabilized. By Jun 11, 2025 6:04 AM UTC, most affected services had recovered in the major regions, though some dependencies required additional stabilization. The outage lasted approximately 27 hours and 15 minutes, from the initial down event to ongoing recovery.

User reports were spread across time zones and regions (including the United States, United Kingdom, Canada, India, Vietnam, and South Africa), underscoring the broad geographic reach of the disruption. The incident affected a large number of Salesforce components in both North America and Europe, with multi-region impact on marketing, sales, and CPQ operations.

The Salesforce outage began at Jun 10, 2025 2:39 AM UTC and affected dozens of backend data components across the EMEA and North America regions, causing widespread disruption to core CRM functionality, Marketing Cloud and related services. Users experienced timeouts and unavailability of key Salesforce features, with reports of load failures across multiple geographies. The incident persisted for about 28 hours, and recovery progressed in waves, with most core services returning to operation by Jun 11, 2025 6:04 AM UTC.