Salesforce Global Outage
Points and comments are a snapshot, not live.
Salesforce suffered a global outage affecting thousands of instances across multiple services.
Salesforce's status page lists 3243 instances with widespread 'Service Disruption' indicators across Americas, Asia Pacific, and EMEA regions. Affected services include Marketing Cloud, Commerce Cloud, Experience Cloud, Heroku, Tableau, MuleSoft, and Spiff. Incident details (link: https://status.salesforce.com/incidents/20004433) reference a 'legacy login service' issue. The company attempted rolling restarts on impacted instances but abandoned that approach. A fix is reportedly rolling out.
What commenters are saying
Commenters mocked the status page for its overwhelming list of instance IDs and lack of clear outage information, calling it 'the most salesforce thing ever.' Some defended it as useful for customers who know their pod. Speculation on the cause ranged from DNS (a common joke) to AI automation load from Dreamforce. Several noted that the incident page reveals attempts at rolling restarts that failed, with one saying 'rebooting is the first step' to partition the problem space. Critics of Salesforce's API and integration complexity emerged, while others defended the standard REST APIs as straightforward.