3 ms·
Cause: Legacy Salesforce login service got into a resource-exhaustion cascade. Fix: Rolling some unspecified fix they proved in testing out over the fleet seem
by fhub 16d ago
Cause: Legacy Salesforce login service got into a resource-exhaustion cascade.
Fix: Rolling some unspecified fix they proved in testing out over the fleet seemingly very slowly (After their earlier attempts to roll something out faster failed).
Details at https://status.salesforce.com/incidents/20004433 https://status.salesforce.com/incidents/20004433
- dd8601fn 16d agoI wonder if “legacy login” is the shared login gateway. It’s optional but everyone uses it. And it was flaky for an hour or so, like two months ago.
- kgermino 16d agoAnd while I haven’t actually done my homework, the push to email-based login seems like it’s really pushing people to start using their own custom domains for logging in
- ubertaco 16d agoCoincidentally, Salesforce just laid off the senior engineering lead on their shared login service team who 2 months ago was describing the practices his team follows to keep 99.95% uptime on that shared login service (this guy: https://www.linkedin.com/posts/patricktprice_engineeringmanagement-reliability-activity-7475257204628099075-LrN7 https://www.linkedin.com/posts/patricktprice_engineeringmana...) Layoffs are usually short-term money-savers at long-term cost, but hot damn this is the shortest short term I've ever seen.