Salesforce Outage History

The incident affected two Anypoint components in APAC and North America: Asia Pacific - Anypoint Management Center - JP / Runtime Manager, and North America - Anypoint Partner Manager v2 - US / Anypoint Partner Manager v2. The issue began at 9:39 PM UTC and APAC components returned to normal by 10:54 PM UTC, while the North America component remained degraded until 1:19 AM UTC. The overall duration was roughly 3 hours and 40 minutes, with users in these regions experiencing intermittent access and slower responses to Anypoint management and partner management functions.

Salesforce issued 4 official status updates during the incident, documenting the degraded state and subsequent recovery. The geographic impact appeared limited to APAC and North America, with no global disruption.

The Salesforce Search component in Asia Pacific (JPN156) experienced a brief degradation beginning at 6:09 AM UTC and resolving by 7:49 AM UTC. The outage lasted about 1 hour 40 minutes and was limited to the Asia Pacific region, affecting users performing searches within that region. Salesforce issued 2 status updates during the incident, with the service returning to normal after the second update.

The Salesforce Journey Builder service experienced regional degradation across multiple regions, with dozens of Journey Builder components in EMEA, North America, and Asia Pacific listed as degraded (warn) starting at 7:09 PM UTC. The incident lasted about 50 minutes and was resolved by 7:59 PM UTC as components returned to up. This broad impact could affect automated journeys, campaigns, and related workflow operations for users in the affected regions.

The outage began at Nov 11, 2025 11:04 AM UTC with Asia Pacific Mobile Connect components DB401023 and DB401025 entering a degraded state. At 12:19 PM UTC, North America Core Service NA253 also entered a degraded condition. NA Core Service recovered at 12:59 PM UTC and APAC Mobile Connect followed with recovery at 1:54 PM UTC. Salesforce issued four status updates during the incident. The total duration from the first report to full recovery was approximately 2 hours and 50 minutes.

Salesforce Tableau Cloud in the Asia Pacific South Korea region experienced degraded performance starting at Nov 10, 2025 2:34 PM UTC for the prod-kr-a Tableau Cloud component. Users accessing dashboards and visualizations hosted in this regional instance may have faced slower response times and intermittent access. The degradation persisted for about 11 hours and was resolved by Nov 11, 2025 1:34 AM UTC.

From Nov 10, 2025 11:54 AM UTC to Nov 10, 2025 1:09 PM UTC, Salesforce Core Service components in the Europe, Middle East and Africa (EMEA) region experienced degraded performance with 19 Core Service components listed as degraded (warn) on the Salesforce status page. The degradation affected a broad set of Core Service components across the EMEA region, and users in those areas may have experienced slower responses or intermittent access to Salesforce services.

The Salesforce Asia Pacific IND92 Core Service briefly degraded beginning at 10:09 AM UTC and was resolved by 10:24 AM UTC, lasting about 15 minutes. The issue affected only the APAC IND92 Core Service and returned to normal within that short window. Status updates indicated the component recovered and service returned to full operation.

Salesforce experienced a brief degradation affecting Spiff components in EMEA EU1 and North America US1. The incident began at 9:44 PM UTC and was resolved by 10:29 PM UTC, lasting about 45 minutes. The provider issued 2 official updates during the incident, and users may have encountered intermittent performance issues or degraded functionality when using Spiff-related features during that window.

Salesforce experienced a brief regional degradation of the Asia Pacific IND92 Core Service. The issue began at 6:04 PM UTC and was resolved by 6:34 PM UTC, lasting about 30 minutes. The incident was isolated to the Asia Pacific IND92 Core Service component, with users potentially encountering intermittent access or performance issues during that window. The Salesforce status page indicated a rapid degradation followed by restoration within this period.

From Nov 5, 2025 9:19 AM UTC Salesforce began reporting degraded performance affecting B2C Core components across multiple pods in EMEA, North America, and Asia Pacific, with Einstein Bots also impacted. End-user experiences tied to B2C Core and bot interactions could have been slow or intermittently unreliable across dozens of components.

The Salesforce status page issued regular updates throughout the incident (13 updates in total), detailing ongoing degradation and eventual recovery. By Nov 5, 2025 3:14 PM UTC most affected pods and Einstein Bots had returned to service, marking the end of the incident after roughly 6 hours of degraded performance. The event appeared region-wide rather than confined to a single data center.