On 10 November, Salesforce Core instances ran slow for roughly two hours, and a separate security advisory affecting Talent Rover integrations opened later the same day. Both issues trace back to Salesforce's own systems, not anything in your setup.
Started
15:12 UTC
Duration
Lasted 1h 47m
Source
IsDown
Next time
Salesforce is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
The first incident started at 15:12 UTC and ran for 1 hour 47 minutes, affecting the Account Engagement component. Salesforce's own updates describe customers on affected Core instances seeing slower-than-normal page load times across most operations. At 15:40 UTC Salesforce said it was investigating errors and reviewing recent changes and slow-running requests on the affected instances. By 15:54 UTC the company had narrowed its thinking, pointing to a large number of customer orgs that had moved between instances over the weekend, plus two recent changes common to some of the affected instances. At 16:18 UTC Salesforce issued an impact radius increase, saying the problem was broader than first understood and that customers on the newly added instances would start receiving their own communications. The 16:21 UTC update said load times were stable but still slower than normal, with recovery not yet confirmed, and mentioned a planned change to move the affected instances to a different part of the caching system. No update after that is on record, so whether the caching change resolved things is not stated. A second, separate incident opened at 23:16 UTC, a security advisory about Salesforce disabling Talent Rover integrations. No further updates have been filed for that one, and it remains open with no stated cause or resolution plan. No user reports were filed during the window for either incident.
Learning
This is a case where the fault sat inside Salesforce's own infrastructure, in how instances route load and cache requests, a layer you cannot see or test from outside. Pinging your own endpoints or watching your application's response times would show your product working fine even while the underlying instance degraded pages for everyone on it, because the slowdown originated upstream of anything you control. Salesforce's own account of the problem shifted as it investigated, starting with a narrow set of instances and widening the impact radius an hour later, which is a normal pattern for incidents where the provider is still mapping the damage as it goes. The second incident, a security advisory with no updates since it opened, shows how little detail some incidents carry even when they stay open for hours. For anyone running a product on top of Salesforce, 123 incidents over the last 90 days with a median duration of 2 hours 2 minutes is the baseline rate to expect, so isolated slowdowns like this one are not unusual. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.