Salesforce Outage History

Salesforce ITA14 Core Service in the EMEA region experienced a brief degraded state beginning at Jul 3, 2025 9:59 PM UTC and was restored by Jul 4, 2025 1:19 AM UTC, totaling about 3 hours and 20 minutes. The impact was confined to the EMEA - ITA14 / Core Service, with users likely facing intermittent access or slower performance during the window. Salesforce communicated the issue via two status updates, noting a degradation followed by restoration as services returned to normal. The incident concluded with the core service fully operational again; there was no indication of a broader global impact.

The Salesforce EMEA - ITA14 Core Service entered a degraded state beginning at 9:49 PM UTC and was restored at 1:19 AM UTC, lasting about 3 hours and 30 minutes. The EMEA region likely experienced intermittent access or reduced performance for Salesforce features tied to this core service. Salesforce documented the incident on its status page, listing the EMEA ITA14 Core Service as degraded and providing updates as the situation evolved. The provider published three official updates during the incident before the service returned to normal.

The incident began at 12:40 AM UTC when Salesforce Data Processing Features across North America, EMEA, and Asia Pacific entered a degraded state. In the following hours, Core Service components in Europe and APAC also showed degraded performance as the issue progressed.

The status updates described a staggered impact across regions and services, with several components listed as degraded before restorations began. The situation extended across most of the morning, causing intermittent issues for workflows that rely on data processing and core services. By 10:16 AM UTC, Data Processing Features had been restored, and by 11:14 AM UTC all affected Core Service components were back to normal, marking the end of the incident. Salesforce posted six official updates detailing the recovery progress and regional restorations throughout the event.

Salesforce Core Service components in Asia Pacific (JPN134, IND112, IND104, AP49) experienced a temporary degradation that affected users in the region, with slower responses and intermittent access to Salesforce services. The outage began at Jul 2, 2025 10:54 AM UTC and was resolved by Jul 2, 2025 12:55 PM UTC, lasting about 2 hours and 1 minute. Salesforce posted two status updates during the incident, noting the degraded state and subsequent restoration. The impact was confined to four Asia Pacific Core Service components, and services returned to normal after the incident.

Salesforce Core Service components in the Asia Pacific region experienced a brief degraded performance, affecting four components (JPN134, IND112, IND104, AP49). Users in AP may have encountered slower responses or intermittent access to Salesforce features during the incident.

The outage began at 10:44 AM UTC and was resolved by 12:55 PM UTC. A follow-up update occurred at 10:54 AM UTC. Salesforce issued three status updates as the incident progressed, and all affected Core Service components returned to normal status after the incident.

Salesforce reported a regional degradation beginning with Spiff in North America moving to a degraded state at Jun 30, 2025 5:39 PM UTC. By Jul 1, 2025 3:51 AM UTC, dozens of North America Service Cloud Messaging Channels were listed as degraded. Some channels began recovering by Jul 1, 2025 9:46 AM UTC and Jul 1, 2025 10:01 AM UTC, while others remained affected. In Europe, three EMEA B2C Core pods (POD219, POD270, POD318) briefly went down starting at Jul 1, 2025 4:04 PM UTC and were back to up by around Jul 1, 2025 5:04 PM UTC to Jul 1, 2025 5:14 PM UTC.

Salesforce reported degraded messaging for Service Cloud Messaging Channels in North America beginning around Jun 30, 2025 5:29 PM UTC, with many North American regions listed in a warning state. Concurrently, a regional outage affected the B2C Core components in Europe, with POD219, POD270, and POD318 going down and then recovering, disrupting B2C workflows in that region. The incident affected messaging delivery and B2C service functionality across multiple components and regions and progressed through several status changes on the Salesforce status site.

The Salesforce Asia Pacific - JPN158 Core Service experienced a brief degraded state beginning at Jun 30, 2025 2:39 PM UTC and resolving by Jun 30, 2025 3:29 PM UTC, lasting roughly 50 minutes. The issue was regional to the Asia Pacific area (JPN158) and affected users relying on the core service in that region. Salesforce communicated the incident on its status page, issuing two updates that described the degradation and subsequent recovery.

Salesforce Asia Pacific - JPN158 / Core Service experienced a brief degradation, with the APAC core component entering a degraded state at Jun 30, 2025 2:34 PM UTC and again at Jun 30, 2025 2:39 PM UTC before recovering. The service was fully restored by Jun 30, 2025 3:29 PM UTC, for a total duration of about 55 minutes. The incident affected only the Asia Pacific region's Core Service for JPN158; no other Salesforce services or regions were indicated as impacted. The Salesforce status page logged three updates during the incident describing the degraded state and subsequent recovery.

Salesforce experienced a regional degradation in Asia Pacific Core Service components, impacting users relying on those services. The incident began at 8:29 AM UTC when Asia Pacific Core Service components KOR4S, KOR2S and ARE2S were listed as degraded. Over the next hours, additional components KOR6 and ARE12 were progressively marked as degraded, with a total of five official status updates issued during the incident. By 1:49 PM UTC the affected components were returned to normal operation.

Impact was regional in scope (Asia Pacific) and largely limited to Salesforce Core Service in those regions; users may have experienced slower performance or intermittent access to features tied to the affected components. The incident was resolved by 1:49 PM UTC with services restored to full operation across the listed components.