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 |
|---|---|
| 3:56 PM | Salesforce says the remaining impact has been narrowed to a subset of Hyperforce instances. First-party environments were not impacted. Mitigation is now in place across nearly all affected instances, with targeted restarts and manual recovery actions continuing on the remaining instances. |
| 3:26 PM | Salesforce is seeing signs of recovery, with many customers coming out of impact. Manual restarts continue for instances where the automated fix did not fully resolve the issue. |
| 2:57 PM | Salesforce completed the next phase of the rollout to the remaining impacted instances. Manual restarts continue for instances where the automated fix did not fully resolve the issue. |
| 2:30 PM | Salesforce says the impact radius is narrower than initially understood and is removing instances that have not experienced an impact from the incident communications. Impacted instances will continue to receive updates. |
| 2:00 PM | Salesforce completed the next phase of the rollout and is manually restarting instances where the automated fix did not fully resolve the issue. Reports of scheduled jobs not running as expected are also being investigated. Salesforce says the impact radius is narrower than initially understood and will remove unaffected instances from incident communications. |
| 1:13 PM | Salesforce determined that the rollout did not fully complete for several instances, leaving some customers affected by the original issue. The company is reapplying the fix. Some customers may need to clear cached data or restart their session for full recovery. |
| 12:13 PM | The region-by-region rollout is progressing, and most instances are recovering. Some customers may still see errors until Salesforce completes manual restarts on affected instances. No confirmed resolution time is available. |
| 11:43 AM | The rollout is progressing region by region, with services returning to normal in completed regions. Salesforce continues monitoring the rollout while working on a permanent fix. |
| 11:41 AM | The rollout is progressing region by region, with Salesforce reporting improvement. No confirmed completion time yet. GovCloud customers have been confirmed to be out of impact. Some customers may still experience severe delays, intermittent errors, service access issues, and support case creation problems. |
| 11:19 AM | A fleetwide rollout is in progress, and customers are beginning to see services return to normal. Salesforce is also working on a code-level permanent fix. |
| 10:56 AM | Salesforce successfully validated the fix on a test instance and began rolling it out fleetwide to all impacted instances. |
| 10:31 AM | Salesforce is testing a fix on a test instance. Once validated, the fix will be rolled out fleetwide. Customers continue to experience severe delays, intermittent errors, service access issues, and problems creating support cases. |
| 10:18 AM | Salesforce says increased load on one of its core system components limited its capacity to process requests. Engineers are working on a fix to resolve the issue and restore services |
| 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.
10:18 AM GMT, September 16, 2026 – Core System Under Increased Load
Salesforce has provided another update on the ongoing service disruption, stating that one of its core system components experienced increased load, which limited its capacity to process incoming requests.
The company says its engineering teams are currently working on a fix to address the issue and restore normal service.
The latest update indicates that the outage is still ongoing, with customers potentially continuing to experience delays, errors, and difficulties accessing affected Salesforce services.
Salesforce has not yet announced full service restoration.
10:31 AM GMT, September 16, 2026
Salesforce says it is pursuing the fastest path to restore services and is currently testing its fix on a test instance.
Once the test is validated, Salesforce plans to roll out the fix fleetwide across the affected infrastructure.
Customers continue to experience severe delays, intermittent errors, inability to access some services, and problems creating support cases.
10:56 AM GMT, September 16, 2026 – Fix Validated, Fleetwide Rollout Begins
Salesforce says it has successfully validated the fix on the test instance and will now roll out the fix fleetwide to all impacted instances.
The company says it will provide another update within 30 minutes or sooner if additional information becomes available.
11:19 AM GMT, September 16, 2026 – Fleetwide Rollout Underway
Salesforce says a fleetwide rollout is in progress, with customers beginning to see their services return to normal.
In parallel, the company says it is working on a code-level permanent fix.
Salesforce will provide another update within 30 minutes or sooner if additional information becomes available.
11:41 AM GMT, September 16, 2026 – Regional Rollout Shows Improvement
Salesforce says the rollout is progressing region by region and that it is seeing improvement.
The company does not currently have a confirmed completion time. Salesforce also confirmed that GovCloud customers are no longer impacted.
However, customers may continue to experience severe delays, intermittent errors, inability to access some services, and problems creating support cases while the rollout continues.
12:13 PM GMT, September 16, 2026 – Most Instances Recovering
Salesforce says the rollout is progressing region by region, with most instances now recovering.
However, some customers may continue to see errors when accessing Salesforce services until a manual restart is completed on their individual instance.
Salesforce has not provided a confirmed resolution time and says another update will be provided within 30 minutes or sooner if additional information becomes available.
11:43 AM GMT, September 16, 2026 – Services Returning to Normal
Salesforce says the rollout is progressing region by region, with services returning to normal in regions where the rollout has been completed.
The company is continuing to monitor the rollout and is also working on a permanent fix.
1:13 PM GMT, September 16, 2026 – Fix Being Reapplied
Salesforce says it has determined that the rollout did not fully complete for a number of instances, meaning some customers may still be experiencing the original issue.
The company is now reapplying the fix to the affected instances.
Salesforce also warns that some customers may need to clear cached data or restart their session to fully recover access to the affected services.
2:00 PM GMT, September 16, 2026 – Manual Restarts Underway
Salesforce says it has completed the next phase of its rollout and is now manually restarting instances where the automated fix did not fully resolve the issue.
The company has also received reports that scheduled jobs are not running as expected for some customers who have regained access to Salesforce services. Salesforce says it is investigating the issue.
The investigation has also determined that the impact radius is narrower than initially understood. Salesforce will remove instances that have not experienced an impact from the incident and they will no longer receive communications about the outage.
Impacted instances will continue to receive updates as the recovery process continues.
2:30 PM GMT, September 16, 2026 – Impact Radius Narrowed
Salesforce says its investigations have shown that the impact radius is narrower than initially understood.
The company will remove instances that have not experienced an impact from the incident communications. Impacted instances will continue to receive updates.
Salesforce apologized for the inconvenience and said another update would be provided within 30 minutes or sooner if additional information becomes available.
2:57 PM GMT, September 16, 2026 – Rollout Completed for Remaining Impacted Instances
Salesforce says it has completed the next phase of the rollout to the remaining impacted instances.
The company continues to manually restart instances where the automated fix did not fully resolve the issue.
Affected customers may continue to experience severe delays, intermittent errors, inability to access some services, and support case creation issues while the recovery process continues.
3:26 PM GMT, September 16, 2026 – Recovery Signs Reported
Salesforce says it is seeing signs of recovery, with many customers now coming out of impact.
The company continues to manually restart instances where the automated fix did not fully resolve the issue. Salesforce has not provided a confirmed resolution time.
Customers may still experience severe delays, intermittent errors, inability to access some services, and problems creating support cases while recovery continues.
3:56 PM GMT, September 16, 2026 – Impact Narrowed to Hyperforce Instances
Salesforce says it has narrowed the remaining impact to a subset of Hyperforce instances. The company confirmed that first-party environments were not impacted.
The mitigation is now in place across nearly all affected instances, while Salesforce continues targeted restarts and manual recovery actions on the remaining affected instances.
Some customers may continue to experience severe delays, intermittent errors, inability to access some services, and issues with support case creation.
Status: Ongoing investigation
So what is Salesforce NOT telling us?
Oh yeah, what’s an “instance”?
Everything is PR vetted corporate speak at this point unfortunately
On Reddit, it is suspected that there is a connection with the current event, in whatever context
Nah nothing like that. I assure you