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 <a href="https://status.salesforce.com/incidents/20004433" rel="nofollow">https://status.salesforce.com/incidents/20004433
And 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
Coincidentally, 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: <a href="https://www.linkedin.com/posts/patricktprice_engineeringmanagement-reliability-activity-7475257204628099075-LrN7" rel="nofollow">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.
fhub · · focus · HN ↗
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 <a href="https://status.salesforce.com/incidents/20004433" rel="nofollow">https://status.salesforce.com/incidents/20004433
dd8601fn · · focus · HN ↗
It’s optional but everyone uses it. And it was flaky for an hour or so, like two months ago.
kgermino · · focus · HN ↗
ubertaco · · focus · HN ↗
Layoffs are usually short-term money-savers at long-term cost, but hot damn this is the shortest short term I've ever seen.