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
: Salesforce NA core service briefly degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(30 minutes)
The Salesforce North America Core Service NA125 experienced a brief degraded state beginning at and was restored by . The issue affected the North America - NA125 / Core Service component and lasted about 29 minutes, with the incident localized to this region.
Minor
: Salesforce NA125 Core Service briefly degraded in North America
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(40 minutes)
Salesforce experienced a brief degraded performance affecting the North America NA125 Core Service. The degradation began at and was resolved by , lasting about 40 minutes. Users relying on the NA125 Core Service in North America may have experienced slower responses or intermittent issues with Salesforce features dependent on that service. The incident appears isolated to the North America region. The provider issued 3 status updates during the incident.
A brief degraded performance was observed for Salesforce Tableau Cloud in Germany (DUB01), part of the EMEA region. Users may have experienced slower responses or intermittent access while the Tableau Cloud service returned to normal.
Salesforce logged two official status updates during the incident. The issue began at and was resolved by , lasting about 1 hour and 35 minutes. The impact was limited to the DUB01 Tableau Cloud instance in Germany, with no evidence of wider regional effects.
Minor
: Salesforce Tableau Cloud in Germany briefly degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 45 minutes)
The Salesforce Tableau Cloud component in Germany (DUB01) experienced a brief degraded performance starting at . The issue affected user access and performance for Tableau Cloud in the Germany region. The Salesforce status page recorded the component entering a degraded state with updates at and , before returning to normal at . The incident lasted about 1 hour 45 minutes and included three official status updates. A small volume of user reports accompanied the event.
Minor
: Salesforce North America Search briefly degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(52 minutes)
Salesforce Search in North America (USA352) experienced a brief degraded performance, impacting users attempting to use search within that region. The issue began at and was resolved by , lasting about 53 minutes. Salesforce issued two status updates during the incident, first noting the problem and later confirming restoration of normal operation. The disruption was limited to the North America - USA352 / Search component and did not indicate a broader service outage.
Minor
: Salesforce USA352/Search briefly degraded in North America
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 3 minutes)
Salesforce reported a brief degradation of the North America USA352 / Search component, beginning at with a follow-up at . The issue affected search functionality for users in North America, resulting in a degraded search experience for a little over an hour. The component recovered and returned to normal at .
The Salesforce status page issued 3 updates during the incident, indicating a localized regional impact with recovery completed.
Minor
: Salesforce Chat in North America briefly degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 35 minutes)
Salesforce Chat in North America (NA241) was degraded from to , a duration of about 1 hour and 35 minutes. The issue affected the North America - NA241 / Salesforce Chat component, potentially impacting chat availability and performance for users in the region. The incident appeared localized to this component and has since been resolved. The Salesforce status page published two updates during the incident, describing the degraded condition and the restoration of normal operation.
Minor
: Salesforce Chat degraded in North America NA241
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 45 minutes)
Salesforce Chat in North America NA241 experienced degraded performance starting at , with a follow-up update at . The degraded state lasted for about 1 hour and 45 minutes and was resolved by . Users relying on Salesforce Chat in the region may have encountered slower responses, intermittent availability, or reduced functionality during the incident.
Salesforce documented the disruption on its status page, issuing three updates during the event and restoring normal service at . The impact appeared localized to the North America - NA241 Salesforce Chat component, with no indicated widespread disruption to other Salesforce services or regions.
Minor
: Salesforce Core Service in North America briefly degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 30 minutes)
Salesforce Core Service in North America (USA336) experienced a brief degradation beginning at and restored by , lasting about 2 hours and 30 minutes. The incident affected the North America - USA336 Core Service component, with users potentially encountering degraded performance or intermittent access during the window. Salesforce issued two status updates during the event, communicating the degraded state and the subsequent recovery.
Minor
: Salesforce Core Service in North America degraded for 2h40m
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 40 minutes)
The Salesforce North America Core Service (USA336) experienced degraded performance beginning at and was restored by . End users in the region may have faced slower responses or intermittent access during the incident, which lasted approximately 2 hours and 40 minutes and affected the Core Service component in North America.
Salesforce issued 3 official status updates during the incident, documenting the degradation and subsequent recovery. The impact appeared regional to North America (USA336 Core Service) with no confirmed widespread outages across other regions.