UPDATED An hours-long Salesforce outage on Wednesday hit customers with severe delays, intermittent errors, and inability to access some services, according to the SaaS vendor's status page. The outage hit hundreds of instances throughout the world, including the USA, Japan, India, the UK, France, and Germany. The service disruption was first reported around 0930 BST (0830 UTC) on September 16. An update at 1219 BST (1056 UTC) said the company had validated and rolled out a fix, and customers were seeing service return to normal. However, as of 1500 BST (1400 UTC), the company said that the fix had not completely restored all instances of the problem, and it had "received reports of scheduled jobs not running as expected for some customers who are now able to access the service." A previous update at 1010 BST (0910 UTC) by the CRM giant said its investigation indicated that "requests are stalling while waiting on a response from an internal login service, which is using up available server resources." The vendor added: "Customers continue to experience severe delays, intermittent errors, and inability to access some services. This also affects support case creation." Salesforce's customer list is a roll-call of global giants from all industries, including include Amazon, Walmart, Coca-Cola, Toyota, and IBM. The outage came at a bad time for the SaaS company. Yesterday, it kicked off its annual conference, Dreamforce, in San Francisco. More than 40,000 people are expected to attend in person, with in excess of 200,000 people registered to attend online. Updates to the situation, which is still ongoing as of 1725 UTC, are below. ® Updated at 2020 BTS (1920 UTC) Salesforce says that the incident has now been resolved. Updated at 1722 BTS (1622 UTC): Salesforce says that the impact radius is narrower than they originally thought. They will continue to update impacted instances. Updated at 1650 BST (1550 UTC): Salesforce has completed the next phase of its rollout and narrowed the remaining disruption to a subset of Hyperforce instances. Its first-party environments are unaffected. Mitigation is in place across nearly all affected instances, although the company continues targeted restarts and manual recovery work where the automated fix has not fully resolved the problem. Some customers could still experience delays, errors, and problems accessing services or creating support cases. Updated at 1522 BST (1422 UTC): Salesforce said it was manually restarting instances where the automated fix hadn't fully resolved the issue, and that it was still receiving reports of scheduled jobs not running as expected for some customers who were able to access the service. It also said that the "impact radius" of the problem was "narrower than initially understood." Updated at 1429 BST (1329 UTC): Salesforce said the rollout had not completed successfully on some instances, leaving customers exposed to the original problem. The company is reapplying the fix and warns that some users might need to clear cached data or restart their sessions to recover fully. Updated at 1407 BST (1307 UTC): Salesforce said most instances were recovering as the rollout progressed. Some customers may continue to encounter errors until their instance is manually restarted, and the company has yet to confirm when the incident would be fully resolved. Updated at 1327 BST (1227 UTC): Salesforce said services were returning to normal in regions where the rollout had been completed. The company continues to monitor the deployment while working on a permanent fix. Updated at 1300 BST (1200 UTC): Salesforce said the fix was being deployed region by region and that service was improving, although it had no confirmed completion time. GovCloud customers were no longer affected, but others could continue to experience severe delays, intermittent errors, and problems accessing some services or creating support cases. Updated at 1227 BST (1127 UTC): Salesforce said the fix was being rolled out "fleetwide" and that customers were seeing service return to normal. Updated at 1200 BST (1100 UTC): Salesforce said the fix had been successfully validated on a test instance and would now be deployed across all affected instances. Updated at 1142 BST (1042 UTC): Salesforce said increased load on a core system component had limited its capacity to process requests. The company is testing a fix on one instance and plans to deploy it across its fleet once validated. Updated at 1109 BST (1009 UTC) on September 16, 2026, to add: Salesforce said in its latest update that it is "no longer pursuing restarts as a path to remediation. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation."

One of the main motivations for quitting Microsoft 365 and adopting Google Workspace is spite, an emotion that sadly doesn’t produce a return on investment. The source of that disappointing news is Domenico Scriva, a senior principal analyst at Gartner, who today told the firm’s IT Symposium event in Australia that moving between the suites is also unlikely to save buyers much money. He pointed out that Google Workspace licenses are cheaper than the E5 bundle that is Microsoft’s most popular M365 license, but that Google’s suite doesn’t cover telephony, security, business intelligence, or an OS license. By the time users add all those bits to Google Workspace, he thinks they will pay $2 a month more than the cost of Microsoft’s suite – even after considering the fact that Google bundles its Gemini AI with Workspaces but Microsoft charges extra for Copilot. Scriva said Google’s suite can be more cost effective when paired with an Apple Mac or Chromebook. Mac users get lower costs because their machines last longer than PCs, while Chromebook owners save on hardware purchase price but need to replace their machines more often. Those numbers don’t consider the complexity of migrating between the suites, and the cost of moving. Scriva said dependencies built into either ecosystem are a likely source of migration complication, and the need for user training is another element that those who contemplate migrations sometimes neglect. The analyst said he’s seen some M365 users trying to use the threat of migration as a negotiating tactic when renewing their Microsoft deals. He said that won’t work if you leave it too late, because Microsoft knows it’s not possible to make the move quickly. He therefore advised starting work on a migration almost as soon as you sign a three-year M365 deal, because it takes at least two years to get it done. If you do decide to move, he recommended having a specific outcome in mind, rather than just swapping one suite for another. Productivity suites have scarcely changed in 30 years, he said, so it’s currently hard to see an outcome that makes a move worthwhile. Happily, Scriva thinks AI may soon change that. He thinks we’re in a new wave of development of productivity suites in which AI assists with content creation. An imminent third wave, he predicted, will properly shake up the market by removing the need to use individual apps like word processors or presentation graphics packages, which he thinks will be replaced by some kind of AI interface that allows users to express what they want to do and then sit back and watch as their suite has a crack at the job. ®