Salesforce experienced a major service disruption on September 16, 2026, leaving customers across multiple regions facing delays, intermittent errors, and difficulty accessing parts of the platform. The incident affected hundreds of Salesforce instances and became a major service-status story for businesses using the CRM platform.
The disruption began during the second day of Dreamforce in San Francisco. Salesforce later identified a problem involving requests waiting on an internal login service, which increased the load on a core system component and reduced its ability to process requests.
Salesforce engineers tested a fix and began deploying it across affected instances. Service gradually returned as the fix moved through different regions.
For U.S. customers, the incident began at about 3:50 a.m. Eastern Time. The disruption was not limited to one Salesforce instance. Reports indicated impacts across the United States and other major markets, including the United Kingdom, France, Germany, Japan, and India.
What Happened to Salesforce on September 16?
The incident began early Wednesday morning in the United States. Customers soon encountered a range of problems while using Salesforce.
The symptoms varied between organizations and instances. Some customers experienced substantial delays. Others encountered intermittent errors or could not access particular services.
The problem also affected support workflows. Salesforce reported that some customers were unable to create new support cases through its Help portal while the incident was active.
This made the disruption more significant for organizations that rely on Salesforce for customer service and internal business operations.
Salesforce initially investigated the problem across multiple instances and regions. Engineers later determined that requests were stalling while waiting for responses from an internal login service.
That condition placed additional demand on available server resources. As the load increased, Salesforce services began experiencing degraded performance and access problems.
The company moved away from simply restarting affected systems and instead developed a broader fix.
When Did the Salesforce Outage Start?
The service disruption began at approximately 7:50 a.m. UTC on September 16.
For customers in the United States, that translated to about 3:50 a.m. Eastern Time.
The first phase involved investigation. Salesforce initially warned that customers could experience severe delays, intermittent errors, and an inability to access some services.
The company continued publishing status updates as engineers investigated the underlying problem.
Later updates provided more information about the technical issue and the steps being taken to restore normal operation.
By the middle of the incident, Salesforce had tested a solution on an individual instance. Engineers then validated the fix before beginning a broader rollout.
The recovery process took place region by region rather than through a single immediate switch.
What Services Were Affected?
The disruption affected Salesforce’s core platform environment and multiple instances.
Customers reported problems with basic platform access, delays, errors, and unavailable functions.
The exact impact depended on the customer’s Salesforce instance and the services being used.
Not every Salesforce customer experienced identical symptoms. Some organizations could access portions of the platform while encountering problems with particular functions.
Others experienced much more significant disruption.
This distinction matters because a global platform incident does not necessarily mean every Salesforce product becomes unavailable at the same moment.
Salesforce operates a large collection of instances and services. Their operational status can differ even during a broad incident.
For that reason, customers checking their own environment need to look at their specific instance status rather than relying only on reports from other organizations.
Why Were Salesforce Users Seeing Errors?
The company’s investigation identified a problem involving an internal login service.
Requests were reportedly waiting for responses from that service. The resulting buildup consumed available server resources and limited the platform’s ability to process additional requests.
That created the conditions for the delays and errors customers were seeing.
The explanation is important because it differs from a simple website outage.
A customer might still reach a Salesforce page while experiencing problems after attempting to perform an action. Another user could encounter an error while trying to open a service or retrieve information.
The result depended on the request being processed and the affected Salesforce environment.
Salesforce’s later updates indicated that engineers had identified a fix and were testing it before deploying it broadly.
Was Salesforce Completely Unavailable?
No single status applied equally to every customer.
The incident affected hundreds of instances, but customers experienced different levels of disruption.
Some users could continue accessing Salesforce while encountering slower performance. Others faced intermittent failures or could not access certain services.
The distinction between partial and complete availability is particularly important during large cloud incidents.
A customer may successfully sign in while a particular workflow remains unavailable. Another organization may experience more severe access problems because its instance is affected differently.
Therefore, a user being able to open Salesforce does not mean the entire platform is operating normally.
Likewise, one customer’s successful access does not mean another customer’s outage is unrelated to the broader incident.
How Long Did the Disruption Last?
The incident lasted for several hours as Salesforce investigated the cause, tested a solution, and deployed the fix.
The company first worked to understand why requests were stalling. Engineers then tested a fix in a controlled environment.
Once the solution was validated, Salesforce began rolling it out across affected instances.
Recovery was gradual.
The company reported that customers were beginning to see services return to normal as the fix was deployed. Salesforce continued monitoring the rollout while individual regions recovered.
This approach meant that service availability could improve at different times for different customers.
A business that continued seeing errors after the fix began rolling out was not necessarily experiencing a separate incident.
Did the Outage Affect U.S. Customers?
Yes. U.S. Salesforce customers were among those affected.
The incident extended across multiple Salesforce regions. Reports identified affected instances in the United States as well as several international markets.
For American businesses, the disruption could interfere with routine activities involving customer records, service cases, sales operations, internal workflows, and Salesforce-connected applications.
The actual effect depended on each organization’s configuration.
A company using Salesforce mainly for customer records could experience a different impact from a business relying heavily on Salesforce for support, automation, reporting, or integrations.
Because Salesforce supports many different business functions, a platform disruption can appear differently from one organization to another.
Why the Timing Was Significant
The disruption occurred while Salesforce was hosting Dreamforce in San Francisco.
Dreamforce is Salesforce’s major annual customer and technology event. The 2026 gathering brought customers, developers, partners, and technology executives together during the same period that users worldwide were dealing with the service disruption.
The timing made the incident especially noticeable.
Customers attending the event were able to follow developments while Salesforce engineers worked on the service problem.
The outage also became a major technology story because Salesforce operates a platform used by organizations across many industries.
Did Connected Services Experience Problems?
Some Salesforce-dependent services reported disruptions during the incident.
That can happen when an application relies on Salesforce for customer information, authentication, case management, data synchronization, or other functions.
One affected company reported that its Salesforce instance was unavailable and that the problem interfered with its ability to receive and respond to certain support requests.
The incident demonstrates how a cloud platform disruption can spread operational effects beyond the platform itself.
However, customers should distinguish between confirmed downstream effects and assumptions.
A company using Salesforce does not automatically experience every consequence of a Salesforce service incident. The effect depends on the specific integration and the functions being used.
Could the Problem Be Your Internet Connection?
Not every Salesforce access problem necessarily comes from the Salesforce platform.
A user could experience an unrelated local network problem, browser issue, authentication problem, or corporate connectivity restriction.
The September 16 incident, however, provided a clear reason for customers to check Salesforce’s service status before changing local configurations.
When multiple employees experience the same problem at approximately the same time, the possibility of a broader platform issue becomes more relevant.
Users should also compare the specific error they see with Salesforce’s current incident information.
If only one employee is affected while colleagues can use the same Salesforce environment normally, additional troubleshooting may be necessary.
What Should Salesforce Users Do During an Outage?
Customers experiencing problems should avoid making unnecessary production changes while a confirmed platform incident is underway.
Instead, users can first identify their Salesforce instance and check its current service status.
Salesforce provides an official Trust system for this purpose. Customers can search for their instance and review its current status and incident history.
During a confirmed incident, businesses should also record important details.
Useful information includes:
- The time the problem began
- The Salesforce instance involved
- The affected feature or service
- Exact error messages
- Whether other employees experience the same problem
- Whether connected applications are also affected
- Whether the issue continues after Salesforce reports recovery
Keeping this information can make follow-up troubleshooting easier.
Businesses should also avoid assuming that repeated browser refreshes or password changes will resolve a platform-wide service problem.
How Can You Check Your Salesforce Instance?
Salesforce provides instance-level status information through its Trust platform.
Customers can search for their Salesforce instance and review its current status. The system also provides information about incidents and maintenance affecting individual environments.
Salesforce describes three important status conditions:
- Maintenance: Planned work is taking place.
- Service Degradation: The instance remains accessible, but certain functions may be unavailable or significantly slower.
- Service Disruption: Customers cannot access the affected instance.
This distinction helps users determine whether a problem involves maintenance, reduced functionality, or a broader access failure.
The Trust system also provides historical information, allowing administrators to review the development of an incident over time.
What Did Salesforce Say About the Fix?
Salesforce engineers identified the technical problem and moved toward a targeted solution after initial investigation.
The company tested the fix on a single instance before deploying it more broadly.
After successful testing, Salesforce began rolling out the solution across affected instances.
The rollout proceeded region by region.
As the fix reached more environments, customers began reporting improved access and returning functionality.
Salesforce continued monitoring the service during the recovery process rather than declaring everything restored immediately.
That approach allowed engineers to watch for additional problems as the change moved across the platform.
Was the Incident Related to a Security Attack?
There is no verified information establishing that the September 16 service disruption was caused by a cyberattack.
The technical explanation provided during the incident focused on requests waiting for an internal login service and the resulting resource limitations.
That is different from publicly identifying a malicious intrusion as the cause.
Customers should therefore avoid treating social media speculation as confirmation of a security incident.
A service outage and a security breach are separate events unless the company or another reliable investigation establishes a connection.
The confirmed information for this incident concerns service availability and the internal processing problem identified by Salesforce engineers.
What Does the Outage Mean for Businesses?
Salesforce serves as a central system for many businesses.
When its services become unavailable or unreliable, employees can lose access to information needed for daily operations.
Sales teams may have trouble retrieving customer information. Support representatives may face delays while handling cases. Managers may be unable to access certain reports or dashboards.
Automated processes can also be affected if they depend on Salesforce services.
The impact differs considerably between companies.
A business with alternative workflows may continue operating while Salesforce recovers. Another organization could depend on the platform for a much larger share of its daily operations.
The incident therefore illustrates why businesses need clear procedures for dealing with cloud-service disruptions.
Latest Status for Salesforce Users
The latest information from the September 16 incident indicates that Salesforce moved into recovery after identifying and validating a fix.
The solution was deployed across affected environments, with service gradually returning to normal.
Customers in different regions could see recovery at different times because the rollout was performed across the Salesforce fleet.
The initial disruption affected hundreds of instances and produced severe delays, intermittent errors, and access problems.
The company also identified a specific internal login-service issue as a key part of its investigation.
Customers who continue to experience problems should check their individual instance status rather than assuming that every remaining error represents the same condition.
Salesforce Outage Timeline
| Stage | What happened |
|---|---|
| Early September 16 | Customers began experiencing access and performance problems. |
| Around 3:50 a.m. ET | The major service disruption began. |
| Investigation | Salesforce examined problems affecting multiple instances. |
| Technical finding | Requests were stalling while waiting for an internal login service. |
| Fix testing | Engineers tested a solution on an individual instance. |
| Validation | Salesforce confirmed that the fix worked in testing. |
| Deployment | The fix began rolling out across affected instances and regions. |
| Recovery | Customers began seeing services return to normal. |
What Salesforce Customers Should Watch Next
The key issue for customers is whether their own instance has returned to normal operation.
Businesses should continue checking service status if they experienced problems during the incident.
If Salesforce reports normal service but a specific organization continues to encounter errors, administrators can investigate whether the remaining issue is local, account-specific, integration-related, or tied to another Salesforce component.
Customers should also retain details of any failed transactions or workflows.
That information can help identify operations that did not complete during the disruption.
For organizations with automated processes, administrators may also need to verify that important workflows resumed correctly after Salesforce service returned.
The Latest Answer for U.S. Users
The September 16 Salesforce incident was a significant global service disruption that affected hundreds of instances and customers in the United States and other countries.
Customers encountered delays, intermittent errors, and difficulty accessing services. Some support-case functions were also affected.
Salesforce later identified a problem involving an internal login service and developed a fix. Engineers tested the solution before deploying it across affected environments.
Service began returning as the fix reached different regions.
The incident does not mean every Salesforce customer experienced a complete platform failure. The impact varied between instances and services.
For U.S. businesses still experiencing problems, checking the status of the specific Salesforce instance remains the most useful first step. Customers can then determine whether the issue matches the broader incident or requires separate troubleshooting.
Have you experienced Salesforce access or performance problems today? Share what you encountered and stay informed as service updates continue.