Salesforce favicon

Salesforce outage on 2026-10-20

salesforce.com
October 2026 20 Minor incident

Salesforce logged two separate incidents on 20 October, affecting 13 components across its USA instance group. The first blocked logins for 31 minutes, and the fault was on Salesforce's side, not yours.

Started

10:28 UTC

Duration

Lasted 31m

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.

Affected components: USA9002, USA9004S, USA9006S, USA9008, USA9010S, USA9012S, USA9014, USA9016S, USA9018S, USA902S, USA9402, USA9404S, USA9406S

What happened?

Salesforce's status page recorded two incidents on 20 October. The first started at 10:28 UTC and was titled "Feature Degradation". Salesforce's own update, posted at 10:40 UTC, said customers weren't receiving outbound emails, including password reset emails and one-time passcodes, which blocked logins outright. Salesforce named a recent change to an email service component as the likely trigger and said it was reverting that change. That incident lasted 31 minutes in total. The second incident started at 18:34 UTC, titled "Proactive Maintenance: Third-Party Certificate Authority Issue", and carried no further updates from Salesforce. It is still open with no resolution time on record. Thirteen components were listed as affected across the day, spanning the USA9000 series instances and USA9400 series instances. Salesforce filed one update across both incidents, and that single filing is the only account available of what went wrong and why. No user reports were logged in this window. Over the last 90 days Salesforce has logged 111 incidents with a median duration of 2 hours 25 minutes, so a 31 minute login block sits well below that median.

Learning

When a login outage traces to outbound email delivery, it fails inside Salesforce's infrastructure, not inside yours. A check that only pings your own application endpoints has nothing to show for this kind of fault, because your endpoints stay reachable the whole time. The login page can load fine while the emails your users need to get past it never arrive. That gap is exactly why external monitoring against the provider itself matters: it catches the half of the system you don't control. Over the last 30 days UptimeRobot logged 38 incidents against this provider with a median duration of 1h 53m, so days like this one are not rare. Your own monitoring covers your half. UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.