Salesforce favicon

Salesforce outage on 2026-10-28

salesforce.com
October 2026 28 Minor incident

Salesforce's Account Engagement component had a rough day on 28 October 2026. A Heroku feature degradation starting at 10:53 UTC ran for 5h 7m, and a separate security advisory opened at 12:31 UTC and is still open. Both are Salesforce's own filings, not something you can see from outside.

Started

10:53 UTC

Duration

Lasted 5h 7m

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: ACCOUNTENGAGEMENT

What happened?

Two separate entries landed against the Account Engagement component on 28 October. The first, logged as a Heroku feature degradation, started at 10:53 UTC and ran for 5h 7m. The only update Salesforce posted, at 15:31 UTC, says most upstream errors had been addressed and that anyone hitting errors while building Node.js packages should retry the build, with a further update promised once normal operations were fully restored. No further update appears on the record, so that is the last word Salesforce has given on resolution. The second entry, a security advisory covering CVE-2026-111497 and CVE-2026-105482 affecting Brotli and Node.js, started at 12:31 UTC and carries no updates at all. It is still marked ongoing. Salesforce's own component list names only Account Engagement as affected across both entries, so the scope they're claiming is narrow and specific, not a platform-wide event. No user reports were filed during the window, so there is nothing from outside Salesforce's own status page to compare against. With only one update across both incidents, you are relying almost entirely on Salesforce's word for what happened and whether it is fixed. Over the last 90 days Salesforce has logged 123 incidents with a median duration of 2 hours 6 minutes, so a 5h 7m incident sits well above typical, and an open-ended security advisory with zero updates is unusual even against that baseline.

Learning

A build pipeline failure and a security advisory are both backend problems that live entirely inside Salesforce's infrastructure, and neither would necessarily show up if you were just pinging your own app's front door. If your product depends on Account Engagement's build or packaging layer, your own uptime checks can stay green while builds silently fail or retry, because your monitoring is watching whether your service responds, not whether a third-party build step upstream succeeded. The single update on the Heroku incident tells you to retry builds manually, which means Salesforce is asking you to work around the problem rather than confirming it is solved. The security advisory having zero updates and no closure time means you cannot tell from the record whether it is being patched, under investigation, or sitting unaddressed. This is the gap that matters: your 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.