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 core services briefly degraded across NA and APAC

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

    Salesforce core services across North America and Asia Pacific experienced a brief degradation affecting 5 core service components (Asia Pacific JPN136, JPN134, JPN144, JPN132 and North America USA890S). Users may have encountered intermittent access or slower performance during the incident. The issue began at and components started returning to normal by after a series of status updates.

    Salesforce issued five status updates during the incident, detailing recovery steps and progress as regional components stabilized. The disruption was regional in scope, spanning North America and Asia Pacific, with services restored as the affected components moved back to normal operation.

    minor icon Minor

    : Salesforce North America Core Service degraded across components

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (4 hours and 25 minutes)

    The Salesforce Core Service in North America entered a degraded state beginning at with multiple Core Service components across CAN and NA regions temporarily listed as degraded (warn). A broad set of components—CAN26, CAN28, CAN34, CAN36, CAN80, CAN46, CAN42, CAN48, CAN44, CAN38, CAN40, CAN52, CAN54, NA125, and NA151—were affected, likely causing slower performance or intermittent access for Salesforce users. The service team issued several status updates as they investigated and mitigated the issue, and the affected components returned to normal, with the incident considered resolved by , for a duration of about 4 hours and 25 minutes.

    minor icon Minor

    : Salesforce NA Core Service degraded across multiple components

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (4 hours and 30 minutes)

    Salesforce North America Core Service experienced degraded performance with 15 components entering a warning state before recovering. Affected components included CAN26, CAN28, CAN34, CAN36, CAN80, CAN46, CAN42, CAN48, CAN44, CAN38, CAN40, CAN52, CAN54, NA125, and NA151. The degradation began at and was resolved by , lasting roughly 4 hours and 30 minutes. Users in North America may have faced intermittent access and slower responses when using Salesforce core features.

    minor icon Minor

    : Salesforce EMEA GBR112 Core Service briefly degraded

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

    Salesforce experienced a brief degradation in the EMEA GBR112 Core Service. The outage began on and was resolved by , lasting about 18 minutes. During this window, users in the EMEA GBR112 region may have experienced slower responses or intermittent connectivity before the service returned to normal. The Salesforce status page showed the GBR112 Core Service moving from an up state to degraded and back to up within a short period, with recovery confirmed shortly after the second update.

    minor icon Minor

    : Salesforce EMEA GBR112 Core Service briefly degraded

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

    The Salesforce EMEA GBR112 Core Service experienced a brief degraded performance. The issue began at with the EMEA GBR112 Core Service entering a degraded state, followed by a second update at . The component returned to normal operation at , for a total duration of about 28 minutes. The impact was regional to the EMEA GBR112 Core Service.

    During the incident, Salesforce posted four updates documenting the degradation and restoration. The event was region-specific to the EMEA GBR112 Core Service, with no broader global impact noted.

    minor icon Minor

    : Salesforce North America Core Service degraded for 2 hours

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

    Salesforce experienced degraded performance affecting North America Core Service components. Thirteen North America Core Service instances were affected (USA9002, USA9004S, USA9006S, USA9008, USA9010S, USA9012S, USA9014, USA9016S, USA9018S, USA9020, USA9022S, USA9024S, USA9026). Users across Salesforce apps relying on these core services may have faced slower responses or intermittent access. The status page listed these components as degraded during the incident.

    minor icon Minor

    : Salesforce Core Service degraded in North America

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

    The Salesforce Core Service in North America experienced degraded performance beginning at . The issue affected 13 Core Service components across the region, potentially impacting access to Salesforce features and causing slower responses for users. The outage lasted approximately 2 hours and 10 minutes, with restoration completed by .

    During the incident, Salesforce published 3 official status updates to communicate progress and restoration. The North America Core Service components progressively returned to normal as the incident concluded.

    minor icon Minor

    : Salesforce North America Core Service briefly degraded

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

    Salesforce Core Service components across North America experienced degraded performance beginning at . The incident affected 13 Core Service components in North America, including USA9002, USA9004S, USA9006S, USA9008, USA9010S, USA9012S, USA9014, USA9016S, USA9018S, USA9020, USA9022S, USA9024S, and USA9026. The outage lasted approximately 2 hours and 15 minutes, with slower responses and intermittent errors affecting Salesforce features and integrations that rely on Core Service. The issue was resolved by .

    major icon Major

    : Salesforce Tableau Cloud outage hits US East and West regions

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

    Salesforce Tableau Cloud experienced a regional outage affecting 7 Tableau Cloud components across US East and US West, disrupting dashboards, reports, and visualizations for users. Affected components included useast-1, prod-useast-a, prod-useast-b, prod-useast-c, 10AY, 10AZ, and UW2B, with users potentially unable to access dashboards or data visualizations during the incident.

    major icon Major

    : Salesforce Tableau Cloud outage hits US East and West regions

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

    The Salesforce Tableau Cloud service in North America experienced a degradation to an outage affecting seven Tableau Cloud components across US East and US West. Users attempting to access dashboards or visualizations hosted on Tableau Cloud may have experienced outages or degraded performance. The incident began at and was resolved by , lasting approximately 1 hour and 40 minutes. The outage progressed from warnings to a full outage before services were restored. The Tableau Cloud team issued six status updates during the incident.

    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