Salesforce favicon

Salesforce outage on 2026-11-04

salesforce.com
November 2026 4 Minor incident

If your Salesforce GovCloud site uses Lightning Web Runtime with rich text or HTML content, you likely saw broken layouts and missing styling for most of the day. The fault sat on Salesforce's side, in a fix that needed two separate deployments across 11 GovCloud instances, and it ran 20h 39m before it was resolved.

Started

12:58 UTC

Duration

Lasted 20h 39m

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, USA9016S, USA9018S, USA9402, USA9404S, USA9406S

What happened?

Salesforce logged one incident on 4 November 2026, starting at 12:58 UTC and running for 20h 39m before resolution. It affected 11 components, all GovCloud instances: USA9002, USA9004S, USA9006S, USA9008, USA9010S, USA9012S, USA9016S, USA9018S, USA9402, USA9404S and USA9406S. The symptom was specific: GovCloud customers running Lightning Web Runtime sites with rich text or HTML content saw missing styling and broken layouts on their site pages. Salesforce's first update noted this was a continuation of an earlier issue, referenced by a separate Trust posting, but said a distinct fix was now needed for this instance set. That fix required extra testing, pushing the first deployment estimate out by six hours. The next update, at 18:51 UTC, said the release was still moving through build and testing steps ahead of deployment to GovCloud. By 04:34 UTC the following day, Salesforce was still finishing build and testing work, apologising for the continued inconvenience. At 06:15 UTC, Salesforce reported testing complete and deployment started on sandbox instances, with production to follow once sandbox validation passed. No update confirming full production resolution appears beyond that point, though the incident is marked closed with a total duration of 20h 39m. No user reports were filed during the window. Over four updates across more than 20 hours, the pattern was one of repeated six-hour delays on a fix that needed to clear testing before it could reach customers.

Learning

This incident was a rendering fault tied to a specific feature, Lightning Web Runtime sites using rich text or HTML, on a specific instance group, GovCloud, not a platform-wide failure. If you weren't running that configuration on one of the 11 listed instances, you would have seen nothing at all, which is why a broad uptime check against Salesforce's main endpoints would likely have stayed green throughout. That's not a contradiction: a check pinging a login page or API endpoint has no way to notice that embedded rich text is rendering without its styling on a GovCloud site page. Salesforce's own updates show the fix itself was slow, needing extra testing time, then separate sandbox and production deployment phases, with six-hour gaps between status checks. For 90 days prior, Salesforce logged 123 incidents with a median duration of 2 hours 9 minutes, so this one ran far longer than typical. Monitoring your own site's uptime tells you your half is fine. It won't catch a provider-side styling regression buried in a specific runtime feature on a specific instance cluster, which is exactly the kind of fault that needs visibility into the provider's own status, not just your endpoint. 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.