2025: The year of the global cloud outage

Learn more
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    magnifying glass icon
    Sign Up
    Salesforce icon
    Salesforce icon

    Salesforce Outage History

    Minor Salesforce outage

    There were 585 Salesforce outages since January 2025 which are summarized below, including incident details, duration, and resolution information.

    Salesforce not working for you?

    Salesforce not working for you?

    minor icon Minor

    : Salesforce North America core services degraded, then restored

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 hours and 10 minutes)

    Salesforce Core Service components across North America experienced degraded performance, impacting a broad set of core services for regional users. The incident began at when affected components transitioned to a degraded state, causing intermittent delays and access issues. The outage lasted about 2 hours 10 minutes and was resolved by . During the incident, Salesforce posted two status updates noting the degraded state and later restoration as services returned to normal. The impact was regional to North America, affecting numerous Core Service instances.

    major icon Major

    : Salesforce Anypoint Platform and CloudHub outage hits multiple regions

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 25 minutes)

    An outage started at when Salesforce reported a wide-scale disruption affecting dozens of Anypoint Platform components and CloudHub deployments. Users experienced login failures and inability to access APIs, dashboards, and management consoles across North America and other regions. The incident impacted CloudHub 1.0 and 2.0 applications, API analytics, authentication, monitoring, and runtime services across multiple regions, hampering integration workflows and enterprise operations.

    Status updates: The provider issued 3 official updates during the incident, detailing ongoing restoration efforts and partial recoveries. The sequence began at , followed by an update at noting some services had been restored in parts, and another at indicating partial recovery for some components. By , at least one area had begun to come back online, though many components remained affected. Anecdotal user reports, including from Auckland, New Zealand, described ongoing logon issues. The outage lasted roughly 1 hour 25 minutes with ongoing recovery and remediation efforts.

    minor icon Minor

    : Salesforce EU50 Core Service briefly degraded in EMEA

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (55 minutes)

    The Salesforce EU50 Core Service in the EMEA region experienced a brief degradation beginning at and resolved at . The issue was limited to the EMEA EU50 Core Service component and resulted in degraded performance or partial access for users in that region during the outage window. The service returned to normal after approximately 55 minutes. The Salesforce status page issued two updates during the incident, communicating the degradation and restoration.

    major icon Major

    : Salesforce Asia Pacific Core Service outage disrupts access

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 hours and 5 minutes)

    The Salesforce Core Service in the Asia Pacific region experienced an outage that affected four Core Service components (IND134, IND126, IND76, IND82). This likely caused regional access interruptions for Salesforce users, impacting authentication, API calls, and data access. The outage began on . Partial recovery for IND134 occurred by , with full restoration for the remaining components by , returning services to normal. Salesforce issued three status updates during the incident to communicate progress, reflecting a regional impact across multiple core service endpoints.

    major icon Major

    : Salesforce APAC Japan Core Service outage affects four components

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 hours)

    An outage in Salesforce Core Service impacted users in Asia Pacific Japan, with four Core Service components offline (JPN144, JPN140, JPN138, JPN146). The incident began at and caused downtime for regional Salesforce functionality until restoration.

    minor icon Minor

    : Salesforce Asia Pacific core service briefly degraded

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (20 minutes)

    Salesforce experienced a brief degradation of its Asia Pacific Core Service (IND114). The incident began at and was resolved by , lasting about 20 minutes. Users in the Asia Pacific region may have experienced slower performance or intermittent access. The provider issued 2 status updates during the incident and returned the service to normal by the end of the window.

    minor icon Minor

    : Salesforce core service in North America briefly degraded

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour)

    Salesforce's North America - USA880S Core Service experienced a brief degradation starting at and resolving by . Users depending on this regional core service may have experienced slower responses or intermittent errors during that hour. The issue was confined to the North America region and affected only the USA880S Core Service component.

    The provider issued two status updates during the incident, first listing the component as degraded at and then confirming restoration at . The impact was localized to this regional core service with no indication of broader Salesforce service disruption.

    minor icon Minor

    : Salesforce North America core services briefly degraded

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 15 minutes)

    The Salesforce core services in North America experienced a brief degradation affecting two components. North America - USA9002 Core Service entered a degraded state at , with North America - USA9008 Core Service following at . Both components returned to full operation by .

    The status page documented these transitions as the incident progressed. The impact was geographically focused on North America, with no indication of widening beyond the two core services.

    minor icon Minor

    : Salesforce Tableau Cloud US-East outage briefly impacts service

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 10 minutes)

    The North America - United States - East (prod-useast-b) component of Salesforce Tableau Cloud briefly went down, affecting Tableau Cloud availability for users in the US-East region. The outage began at and was resolved by , lasting about 1 hour and 10 minutes. Salesforce issued two status updates during the incident to communicate the outage and restoration. There were no Early Warning Signals reported, and this impact was localized to the US-East region.

    minor icon Minor

    : Salesforce regional outage hits North America Managed Runtime

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (5 minutes)

    Salesforce experienced a brief regional outage affecting the North America - Managed Runtime AMER / Managed Runtime - N. Virginia component. The disruption lasted about 5 minutes, beginning at and ending at . Salesforce posted two status updates during the incident as the component recovered and returned to normal. The impact was limited to the North America region; other regions were unaffected.

    Salesforce icon

    Looking for more Salesforce outage stats?

    Get real-time insights and historical data on Salesforce outages.

    Looking to track Salesforce downtime and outages?

    • Receive real-time status updates
    • Show current status on private or public status page
    • Be the first to know if service is down
    • Keep your team informed
    • Monitor alongside other services and websites
    Start monitoring for free