Salesforce is currently investigating a major service disruption affecting multiple instances across all regions, with customers reporting severe delays, intermittent errors, and an inability to access some Salesforce services.
The company acknowledged the disruption on September 16 and said its engineering teams are investigating the issue.
Salesforce Experiencing Global Service Disruption
According to Salesforce’s latest service status update, the incident is affecting multiple instances across all regions.
Customers may experience:
- Severe delays when accessing Salesforce services
- Intermittent errors
- Inability to access certain services
- Problems using Salesforce normally
- Difficulties submitting new support cases through the Salesforce Help portal
Salesforce has not yet provided a root cause for the disruption.
When Did the Salesforce Outage Start?
Salesforce reported that the service disruption began at 7:50 AM GMT on September 16, 2026.
At 8:32 AM GMT, Salesforce publicly acknowledged the service disruption and said it was investigating the issue.
The company subsequently posted another update at 8:45 AM GMT, confirming that the incident was affecting multiple instances across all regions.
Salesforce Says Support Cases May Also Be Affected
One notable aspect of the incident is that some customers are reportedly unable to submit new support cases through Salesforce’s Help portal.
This could make it more difficult for affected customers to contact Salesforce support while the broader service disruption is ongoing.
📬 Stay Ahead of Cyber Threats
Get the latest cybersecurity news, critical vulnerabilities, threat intelligence, tutorials, and exclusive giveaways delivered straight to your inbox. No spam. Unsubscribe anytime.
Subscribe to the Newsletter →Salesforce said it is investigating the issue and will provide another update within 30 minutes, or sooner if additional information becomes available.
Is Salesforce Down Right Now?
Salesforce has officially confirmed a service disruption.
The company has not yet stated that all Salesforce customers are affected, but its latest update says the problem is impacting multiple instances across all regions.
The exact services and instances affected may vary as Salesforce continues its investigation.
Affected Salesforce Instances
Salesforce has listed a large number of impacted instances across multiple regions, including instances in India, the United States, Europe, Asia-Pacific, Canada, Brazil and Australia.
Region Affected Salesforce Instances Asia Pacific AP52, AP53, AP54, AP58, AP60 Australia AUS2S, AUS4S, AUS6S, AUS14S, AUS16S, AUS18S, AUS20S, AUS22S, AUS24S, AUS26S Brazil BRA2S, BRA4S, BRA6S, BRA8S, BRA14, BRA16, BRA18, BRA24S, BRA28, BRA30 Canada CAN2S, CAN4S, CAN6S, CAN8S, CAN20S, CAN26, CAN28, CAN34, CAN36, CAN38 Switzerland CHE2S, CHE4S, CHE6, CHE12, CHE16, CHE18, CHE26S, CHE28, CHE30 Germany DEU2S, DEU4S, DEU6S, DEU8S, DEU10S, DEU12S, DEU14S, DEU16S, DEU20S France FRA2S, FRA4S, FRA6S, FRA8S, FRA12S, FRA24S, FRA32, FRA34, FRA36, FRA42 United Kingdom GBR2S, GBR4S, GBR34, GBR36, GBR38, GBR40S, GBR42S, GBR44S, GBR46, GBR48 India IND2S, IND3S, IND4S, IND6S, IND8S, IND10S, IND12S, IND14S, IND16S, IND18S Indonesia IDN2S, IDN4S, IDN6, IDN8 Italy ITA2S, ITA4S, ITA6, ITA8, ITA10, ITA12, ITA14, ITA16, ITA18 Japan JPN2S, JPN4S, JPN6S, JPN8S, JPN10S, JPN12S, JPN18S, JPN20S South Korea KOR2S, KOR4S, KOR6, KOR8 Singapore SGP2S, SGP4S, SGP6S, SGP8S, SGP10, SGP14 Sweden SWE2S, SWE4S, SWE6S, SWE8, SWE10, SWE12, SWE14, SWE16 United States Multiple USA instances, including USA1, USA2S, USA3S, USA8S, USA20S, USA22S, USA26, USA28S and many others
Salesforce Outage Timeline
| Time (GMT) | Update |
|---|---|
| 10:01 AM | Salesforce says it is no longer pursuing restarts as a remediation path. Customers continue to experience severe delays, intermittent errors, service access problems and support case creation issues. |
| 9:57 AM | Salesforce says an external dependency failure is impacting its legacy login server and blocks an API endpoint as a potential mitigation. |
| 9:10 AM | Salesforce says requests are stalling while waiting for an internal login service and consuming available server resources. |
| 9:10 AM | Salesforce attempts a rolling restart on one impacted instance. |
| 8:45 AM | Salesforce says multiple instances across all regions are affected. |
| 8:32 AM | Salesforce acknowledges the service disruption. |
| 7:50 AM | Service disruption begins. |
Salesforce Investigating the Incident
At the time of publication, Salesforce has not disclosed a confirmed root cause or provided an estimated time for full recovery.
The company is continuing to investigate the incident and says further information will be provided as it becomes available.
For organizations that rely on Salesforce for customer relationship management, sales operations, support, marketing, and other business workflows, prolonged service interruptions could affect access to critical business systems.
We will update this article as Salesforce releases more information about the incident, affected services, and recovery progress.
Latest Update
8:45 AM GMT, September 16, 2026
Salesforce says it is investigating an issue impacting multiple instances across all regions. Customers may experience severe delays, intermittent errors, or an inability to access some services. Some customers are also unable to submit new support cases through the Help portal.
Salesforce says it will provide another update within 30 minutes or sooner if additional information becomes available.
9:10 AM GMT, September 16, 2026
Salesforce says its investigation has identified requests stalling while waiting for a response from an internal login service. The company says this is consuming available server resources and customers continue to experience severe delays, intermittent errors, and an inability to access some Salesforce services.
The issue is also affecting support case creation, meaning some customers may be unable to submit new cases through the Salesforce Help portal.
Salesforce says it has attempted a rolling restart on one of the impacted instances to determine whether the restart resolves the issue.
The service disruption remains ongoing, and Salesforce has not yet announced a full resolution.
9:57 AM GMT, September 16, 2026 – Salesforce Identifies External Dependency Failure
Salesforce now believes the outage is being caused by an external dependency failure impacting its legacy login server.
As a potential mitigation, Salesforce says it is blocking the affected API endpoint while investigating the issue.
Salesforce has also engaged its third-party infrastructure provider to investigate whether its infrastructure is contributing to the disruption. The provider has confirmed that it is not experiencing any infrastructure issues.
The Salesforce service disruption remains ongoing, with customers continuing to experience delays, intermittent errors, service access problems, and issues creating support cases.
10:01 AM GMT, September 16, 2026 – Salesforce Abandons Restart Attempts
Salesforce says it is no longer pursuing restarts as a path to remediation for the ongoing service disruption.
Customers continue to experience severe delays, intermittent errors, and an inability to access some Salesforce services. The outage is also continuing to affect support case creation, preventing some customers from submitting new support cases.
The decision comes after Salesforce previously attempted a rolling restart on one of the impacted instances as a potential way to resolve the disruption.
Salesforce had earlier said it believed the issue was related to an external dependency failure impacting its legacy login server and that it was blocking an API endpoint as a potential mitigation.
The investigation remains ongoing, and Salesforce has not yet announced a full resolution.
Status: Ongoing investigation
