Salesforce Outage History

Two North America components were affected: NA232 Core Service and Anypoint Management Center - US / Runtime Manager. The outage began at Jun 23, 2025 10:04 AM UTC with the Runtime Manager entering a degraded state. A second issue appeared for NA232 Core Service at Jun 23, 2025 2:55 PM UTC, and the Core Service returned to normal by Jun 23, 2025 3:11 PM UTC, with further minor updates around Jun 23, 2025 3:16 PM UTC and Jun 23, 2025 3:26 PM UTC. The Runtime Manager remained degraded until Jun 24, 2025 12:39 AM UTC when it recovered. In total, the Core Service degradation lasted about 5 hours, while the Runtime Manager degradation persisted for roughly 14 hours and 35 minutes, indicating a longer impact on deployment and runtime operations.

The incident generated six official status updates from Salesforce during its course. User reports were limited, with a single observation around 1:30 PM UTC from Philadelphia describing connectivity issues, suggesting the impact was more pronounced in North America.

A regional issue affected Salesforce North America components, including NA232 Core Service and North America - Anypoint Management Center US / Runtime Manager. Users in North America reported degraded access and intermittent connectivity during the incident window. The event began around Jun 23, 2025 9:54 AM UTC with the status evolving through several updates as engineers investigated and addressed the degraded conditions. A Philadelphia-area user report around 1:33 PM UTC indicated connectivity problems, reflecting the early real-user impact.

The outage began at 07:04 UTC on 2025-06-23, affecting dozens of Marketing Cloud Core Service and Mobile Connect components across North America, EMEA, and Asia Pacific. Users experienced outages and degraded messaging capabilities as the affected services went offline. The incident lasted about 20 minutes, with services gradually returning as components came back online.

During the event, Salesforce posted two official status updates detailing the scope and remediation progress. By 07:24 UTC, many Marketing Cloud Core Service and Mobile Connect components had resumed operation across the affected regions, signaling the outage was resolving.

An outage affected three regional Anypoint MQ brokers: US East (us-east-1), Canada Central (ca-central-1), and EU West (eu-west-1), causing temporary messaging disruptions for integrations relying on these brokers. The incident began on 1:19 AM UTC and lasted approximately 35 minutes, with intermittent connectivity to publish/subscribe operations during the window. All three regions eventually recovered.

Salesforce reported an outage affecting Anypoint MQ brokers in US East (us-east-1), Canada Central (ca-central-1), and EU West (eu-west-1). Users could not access messaging brokers, disrupting integrations and workflows that rely on Anypoint MQ. The incident began at 1:09 AM UTC and progressed as key brokers moved between down states across regions.

Over the course of the incident, Salesforce issued six status updates documenting the progression of recovery. ca-central-1 and eu-west-1 began restoring by around 1:41 AM UTC and 1:46 AM UTC respectively, while us-east-1 remained degraded until around 1:54 AM UTC when it returned to normal. The outage lasted roughly 45 minutes to an hour across regions.

The Salesforce North America - CS341 / Core Service experienced a brief degradation. The issue began at 4:24 PM UTC and was resolved by 5:29 PM UTC, lasting about 1 hour and 5 minutes. During the incident, users may have experienced slower performance or intermittent connectivity while the CS341 Core Service was listed as degraded. The Salesforce status page showed two transitions: from up to warn and later back to up, indicating a short-lived degraded period affecting North America.

Salesforce CS341 Core Service in North America experienced degraded performance for about 1 hour and 15 minutes. The issue began at 4:14 PM UTC and was resolved by 5:29 PM UTC. Users accessing the North America CS341 Core Service during this window may have encountered slower responses or intermittent issues. No other regions appeared affected.

During the incident, Salesforce issued 3 official status updates. The North America CS341 / Core Service moved from up to degraded at 4:14 PM UTC and again at 4:24 PM UTC, before returning to normal at 5:29 PM UTC.

Salesforce's North America CS341 Core Service experienced a brief degradation beginning at 4:09 PM UTC. The incident prompted multiple official updates as the North America component moved from up to warn at 4:14 PM UTC and 4:24 PM UTC, with users possibly encountering intermittent access or slower performance. The degraded period lasted about 1 hour 20 minutes, and the Core Service returned to normal at 5:29 PM UTC. The impact appeared regional to North America CS341 / Core Service.

Salesforce published four official status updates during the incident, describing the degraded performance and subsequent restoration.

Salesforce's Core Service experienced a broad outage starting at 8:24 AM UTC, impacting hundreds of Core Service components across North America, Europe (EMEA), and Asia Pacific. Users faced outages or degraded access to Salesforce features, including CRM functions and APIs, across multiple Salesforce instances. The incident progressed in waves as regional components went down in sequence, leading to a widespread disruption across the globe.

The Salesforce Core Service outage began at 8:14 AM UTC and affected core service components across North America, EMEA, and Asia Pacific. Users could have experienced login problems, API access failures, and degraded functionality across Salesforce products that rely on Core Service. The incident expanded to additional regions and components by 10:36 AM UTC, with ongoing degradation reported in status updates.

Salesforce issued multiple status updates throughout the incident, culminating in a recovery by 11:39 AM UTC when most components returned to normal operation. The outage lasted approximately 3 hours and 25 minutes, reflecting broad regional impact before services were restored.