Salesforce logged a 36 minute performance degradation starting at 18:45 UTC on 2 October 2026. The fault sat on Salesforce's side, and Salesforce's own status page is the only source for what happened.
Started
18:45 UTC
Duration
Lasted 36m
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?
Salesforce's status page shows one incident on this day, titled "Performance Degradation", starting at 18:45 UTC and lasting 36 minutes. The only update on record is the opening one, posted at 18:45 UTC: "We're investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information." No further update was filed, and no closing note explains what caused the slowdown or how it was fixed. Salesforce did not name any specific component as affected on this incident, so there is nothing to say about which part of the platform degraded beyond the generic label. No user reports were filed during this window on the record we have. One filing covering 36 minutes is thin, and it means you are relying on Salesforce's own account of severity and scope with no independent confirmation of either. Over the past 90 days Salesforce has logged 129 incidents with a median duration of 2 hours 31 minutes, so this one resolved faster than Salesforce's own typical case. Across all time Salesforce has recorded 2,458 incidents, which gives some sense of how often this status page gets used. Nothing in this record states whether the issue was fully resolved or simply stopped being tracked after 36 minutes. If your product runs on Salesforce, this is the kind of incident that can show up as slow responses or timeouts in your own logs without ever producing a clear root cause from the vendor.
Learning
This incident is a reminder that "performance degradation" from a vendor like Salesforce often means requests still complete but slower, which won't always trip a simple up or down check. An external check watching your own endpoints tells you whether your product is reachable, but it won't catch a slowdown happening inside Salesforce's infrastructure unless that slowdown is severe enough to time out your calls. Salesforce's status page is the only record of this event, with a single update and no post-mortem, so you're trusting their account of both timing and scope. Over 30 days, UptimeRobot's own monitoring recorded 38 incidents tied to Salesforce with a median duration of 3h 37m, a different number from Salesforce's own 90 day median of 2 hours 31 minutes, which shows how differently the same provider can be measured depending on what's doing the watching. Your monitoring covers your half, the requests you send and the responses you get. UptimeRobot now watches the provider's half too, so next time something feels slow on your end, you know which side broke without guessing.
