Salesforce Outage History

Salesforce's Anypoint Management Center - Runtime Manager in North America and Europe experienced a degraded state starting at Jul 9, 2025 11:54 AM UTC. The US region recovered by Jul 9, 2025 12:42 PM UTC, while the EU region remained degraded until Jul 9, 2025 9:14 PM UTC. The incident affected two components and caused intermittent access and management delays for users in those regions. The Salesforce status page issued five updates during the incident, and all affected components returned to up by the end of the event.

The Salesforce Anypoint Management Center runtimes in North America and Europe/EMEA experienced degraded performance starting at Jul 9, 2025 11:44 AM UTC. North America components began returning to normal by 12:42 PM UTC, while Europe/EMEA components remained degraded until 9:14 PM UTC.

During the incident, Salesforce issued six status updates documenting the degradations and restorations. The issue had regional scope, affecting two regions rather than a global outage, and users relying on these runtimes likely faced intermittent access to management functionality until restoration times above.

The Salesforce Anypoint Management Center Runtime Manager in the EU/EMEA and North America regions experienced degraded performance beginning at Jul 9, 2025 11:39 AM UTC. The US/NA component briefly recovered then degraded again, with restoration completed for the US region by 12:42 PM UTC and the EU region not fully restored until 9:14 PM UTC. The incident involved two regional components and was documented through a sequence of status updates, spanning the day as the degraded service gradually returned to normal. In total, seven official updates were issued during the event.

The Salesforce B2C Core service in North America experienced a brief degradation affecting four PODs (POD144, POD238, POD281, POD276). The degradation began at 12:09 AM UTC when these components transitioned to a degraded state, impacting user-facing flows that rely on B2C Core. All four PODs returned to normal operation by 12:29 AM UTC. The provider issued two status updates during the incident, describing the affected components and confirming restoration of services.

Salesforce reported a brief degradation in its North America B2C Core environment affecting four PODs (POD144, POD238, POD281, POD276). The issue began near 23:59 UTC on 2025-07-08 and lasted about 30 minutes, with users potentially experiencing intermittent service performance across affected components. The incident was resolved by 00:29 UTC on 2025-07-09 as status returned to normal.

Salesforce North America experienced a brief degradation affecting two components: Core Service (USA1034) and Search (USA1012). The Core Service entered a degraded state at Jul 8, 2025 2:45 AM UTC and the Search component followed at Jul 8, 2025 3:02 AM UTC. The outage lasted about 1 hour and 20 minutes, with the Core Service restored by Jul 8, 2025 4:05 AM UTC and the Search component fully recovered by Jul 8, 2025 3:56 AM UTC. Salesforce issued seven status updates during the incident to communicate progression across the two NA components and region.

Salesforce reported degraded performance for two North America components: Core Service (USA1034) and Search (USA1012). The incident began at 2:34 AM UTC with Core Service entering a degraded state, followed by degradation in Search. Over the next hour, components fluctuated, with Search returning to normal by 3:56 AM UTC and Core Service restored by 4:05 AM UTC. The incident lasted approximately 1 hour and 31 minutes.

Salesforce reported a brief degraded state across North America Core Service components, affecting 14 CAN-series components (CAN28, CAN52, CAN4S, CAN2S, CAN6S, CAN8S, CAN26, CAN20S, CAN34, CAN36, CAN42, CAN40, CAN80, CAN86S). The issue began at Jul 4, 2025 4:19 PM UTC and was resolved by Jul 4, 2025 4:39 PM UTC, lasting about 20 minutes. During this window, some users may have experienced intermittent access or slower performance across Salesforce core features while the affected components were listed as degraded. The Salesforce status page showed two status transitions—from up to degraded (warn) and back to up—indicating a short-lived disruption rather than a full outage.

Salesforce reported a brief degraded performance across 14 North America Core Service components (CAN28, CAN52, CAN4S, CAN2S, CAN6S, CAN8S, CAN26, CAN20S, CAN34, CAN36, CAN42, CAN40, CAN80, CAN86S). The incident began at 4:09 PM UTC with a degraded state across the listed Core Service components, followed by a second status update at 4:19 PM UTC indicating the issue persisted, and was resolved by 4:39 PM UTC. The service issued three status updates during the incident and users may have experienced degraded access to Salesforce core services in North America during this window.

Salesforce Core Service in North America experienced a brief degradation beginning at Jul 4, 2025 4:04 PM UTC. The issue affected 14 Core Service components across CAN regions (CAN28, CAN52, CAN4S, CAN2S, CAN6S, CAN8S, CAN26, CAN20S, CAN34, CAN36, CAN42, CAN40, CAN80, CAN86S), resulting in degraded performance and intermittent access for Salesforce users in North America. The regional impact lasted approximately 35 minutes before services returned to normal.

Salesforce issued four official status updates during the incident, documenting the degraded state and subsequent restoration. The updates showed a progression from degraded to normal across the affected components, with all services restored by 4:39 PM UTC.