Salesforce Outage History

Salesforce reported a regional degradation affecting Asia Pacific Core Service across five components (KOR4S, KOR2S, ARE2S, KOR6, ARE12). Users in the region likely experienced slower responses or intermittent access to Salesforce features that rely on these core services. The issue began at Jun 30, 2025 8:19 AM UTC and progressed with components entering degraded states; the status page shows updates at 8:29 AM UTC, 10:52 AM UTC, 11:01 AM UTC, and 11:11 AM UTC as components fluctuated between up and degraded. The outage lasted roughly 5 hours and 30 minutes.

Salesforce reported a short outage affecting the EMEA SWE42 Core Service. The incident began at 11:29 PM UTC and was resolved by 11:49 PM UTC, lasting about 20 minutes. The issue affected the EMEA region's Core Service, causing temporary unavailability for users relying on that component. The Salesforce status page posted two updates during the incident, first noting the outage and later confirming restoration of the Core Service.

The Salesforce EMEA SWE42 Core Service briefly experienced an outage that disrupted access for users relying on that regional core service. The outage began at Jun 28, 2025 11:19 PM UTC and included a subsequent update at Jun 28, 2025 11:29 PM UTC before the service was restored by Jun 28, 2025 11:49 PM UTC. The incident lasted roughly 30 minutes and appeared limited to the EMEA region. Salesforce issued three status updates documenting the progression from outage to recovery, with no confirmed impact outside the EMEA region.

The Salesforce Core Service and Data Cloud experienced a broad, global degradation beginning on Jun 26, 2025 2:24 PM UTC. The issue started with Asia Pacific IND8S Core Service listed as degraded and then expanded to North America and other regions, with dozens of Core Service and Data Cloud components marked as degraded (warn) for several hours. The incident demonstrated a widespread impact across multiple geographies as users accessed Salesforce apps and data with slower performance and intermittent errors.

The Salesforce status page issued multiple updates throughout the event, detailing progressive degradation across regions and components and reporting ongoing efforts to stabilize services. By Jun 27, 2025 11:01 PM UTC, many components had returned to normal and the incident moved toward resolution, though some follow-on recovery activity continued beyond that point. The overall event lasted about 8 hours and 37 minutes, with recovery occurring in waves as engineers worked to restore full functionality.

Geographically, the disruption appeared global, affecting North America, Europe, and Asia-Pacific, with a concentration of degraded activity across NA and APAC regions. User experience likely included reduced performance and intermittent access in Salesforce apps and data services during the incident window.

Salesforce Core Service and Data Cloud experienced broad degradation across multiple regions, including North America, Asia Pacific, and Europe, the Middle East and Africa. The incident started at Jun 26, 2025 2:14 PM UTC with Asia Pacific Core Service entering a degraded state, followed by widespread degradations across North America by Jun 26, 2025 3:10 PM UTC. Over the next several hours, dozens of Core Service components across regions toggled between degraded and operational, and Data Cloud components were affected as well. Users could have encountered slower performance, intermittent access, and partial outages depending on the specific region and product involved, with the impact broadest on core services and data platforms.

Recovery began to appear later in the evening, with many components returning to up status around Jun 26, 2025 10:34 PM UTC and continued updates into the night. The incident persisted for several hours, characterized by frequent status changes across a wide array of regional components, reflecting a broad but uneven restoration across Core Service and Data Cloud offerings.

Salesforce reported a partial outage affecting Connect & Mix across North America and Europe, starting at 5:09 PM UTC with all four Connect & Mix endpoints affected. A separate Core Service SWE98 in EMEA briefly degraded starting around Jun 25, 2025 7:47 PM UTC and recovering by Jun 25, 2025 8:57 PM UTC. The Connect & Mix components progressively recovered and returned to normal by 4:44 AM UTC. The outage for Connect & Mix persisted for approximately 11 hours and 35 minutes.

During the incident, Salesforce issued six status updates documenting progress and restoration across five components (four Connect & Mix endpoints plus SWE98 Core Service in EMEA). The geographic impact covered North America and Europe across Azure and AWS infrastructure.

Salesforce reported degraded performance for Connect & Mix across North America and Europe starting at Jun 25, 2025 4:59 PM UTC, affecting four cloud regions: North America - Azure US / Connect & Mix, North America - AWS US / Connect & Mix, EMEA - Azure EU / Connect & Mix, and EMEA - AWS EU / Connect & Mix. The SWE98 Core Service in the EMEA region entered a degraded state around 7:47 PM UTC. The impact likely included slower responses and intermittent access to affected features for users relying on these components.

Salesforce Spiff integration in North America experienced degraded performance beginning at 2:29 PM UTC and was restored by 9:44 PM UTC. The issue affected the SPIFF-APP-GCP / Spiff component and impacted users relying on Spiff functionality within Salesforce workflows. The incident lasted approximately 7 hours and 15 minutes, with the component moving from a healthy state to degraded and back to healthy. The provider issued 2 status updates during the incident. The impact was localized to the North America region.

The Salesforce status page documented the degradation and restoration across two updates, indicating a regional scope that did not appear to affect other regions.

Salesforce Spiff in North America experienced degraded performance beginning at 2:19 PM UTC when the North America - SPIFF-APP-GCP / Spiff component entered a degraded state. A follow-up update at 2:29 PM UTC confirmed the ongoing degraded condition. Users relying on Spiff in North America may have seen intermittent access or slower responses during this period.

The incident lasted approximately 7 hours and 25 minutes, with the Spiff component returning to normal at 9:44 PM UTC. Salesforce issued three status updates during the event, documenting the degradation and subsequent restoration. The impact appeared limited to the North America region.

Salesforce reported a degraded performance issue for the SPIFF-APP-GCP / Spiff component in North America starting at 2:14 PM UTC. The incident saw interim updates at 2:19 PM UTC and 2:29 PM UTC as the Spiff integration remained intermittently impacted. The issue persisted for about 7 hours and 30 minutes and was resolved when the component returned to normal at 9:44 PM UTC. The affected scope was limited to this single Spiff component and did not indicate broader Salesforce impact. The Spiff component recovered to full operation.