Catch up on the essentials
- Salesforce experienced a global service outage on Wednesday, the second day of its Dreamforce 2026 conference, disrupting customers across all three of the company's operating regions.
- The outage affected customers in the United States, United Kingdom, Germany, France, India and Japan, according to Salesforce's status page.
- Attention now turns to the after-hours investor briefing, the next verifiable moment where the company could address the incident and its costs directly.
Selected from this article · 2026-09-16
Read on for the full pictureThe outage and how Salesforce responded

Salesforce experienced a global service outage on Wednesday, the second day of its Dreamforce 2026 conference, disrupting customers across all three of the company's operating regions. According to Salesforce's own status page, the disruption began around 7:50 a.m. UTC and was traced to an internal login service where incoming requests stalled while waiting for a response, consuming available server resources and cascading into broader access failures. Salesforce validated a fix on a test instance and began rolling it out fleetwide by roughly 10:56 a.m. UTC, with independent monitoring services logging the core disruption at around four hours and 22 minutes, though shorter related incidents continued to appear on the company's status tracker later in the day. AInvest reported the cause as increased load on a core component, a framing consistent with the login-service bottleneck described on the status page.
Geographic reach and the Dreamforce backdrop
The outage affected customers in the United States, United Kingdom, Germany, France, India and Japan, according to Salesforce's status page. AInvest described the disruption as worldwide and emphasized that it occurred while the company was promoting its latest AI products and partnerships on the Dreamforce stage, framing the incident as a customer-facing disruption layered on top of the conference's product messaging.
Market reaction and options positioning
Investor response to the outage itself appeared muted. IBTimes reported that Salesforce shares barely budged as investors appeared to shrug off the disruption, while Investors.com noted the stock dipped ahead of an investor briefing scheduled after the close. The share price had already declined before the outage: shares closed Tuesday at $255.65, down 1.46% from Monday's close of $259.43, a move that preceded the incident and therefore cannot be attributed to it. On Wednesday, shares slipped roughly 0.5% in premarket trading to around $254.40, though broader market conditions, including anticipation ahead of the Federal Reserve's interest rate decision, were also weighing on technology stocks that morning, complicating any isolation of the outage's price effect. AInvest reported that options pricing suggested traders were preparing for the stock to move up to 4% in either direction by the end of the week, indicating that uncertainty rather than direction dominated positioning.
Open financial toll and the next milestone
Salesforce has not disclosed a dollar estimate for the outage's cost to the company or its customers, and no independent analyst had published a specific figure as of Wednesday afternoon. The IBTimes analysis noted that, absent an official disclosure or a published third-party analysis, the toll spanning lost productivity, any service credits owed under customer contracts, and reputational impact would likely remain an estimate rather than a confirmed figure unless Salesforce addressed the matter in a future earnings call or regulatory filing. Attention now turns to the after-hours investor briefing, the next verifiable moment where the company could address the incident and its costs directly.
Share this article







