Skip to main content
Salesforce

Communities Degradation on CAN38, USA356, USA358, USA376…

Degraded Lasted 7d 20h · started · Salesforce's page

Level
confirmed
Worst impact
Degraded
Components
Communities
Regions
can38, usa356, usa358, usa376, usa384, usa422, usa442, usa550, usa552, usa578, usa632, usa634, usa640, usa646, usa650, usa652, usa674, usa676, usa680, usa706, usa714, usa730, usa794, usa860, usa924, usa960, usa994, usa1016, usa1018, usa1022, usa1078, usa1082, usa1126
Down Index
43of 100

What to do

  • Check whether you use Salesforce Communities in can38, usa356, usa358, usa376. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 7d 20h it lasted.

    Anything that failed between 2026-10-27 19:00 UTC and 2026-11-04 15:30 UTC may need a replay.
  • Subscribe to Salesforce's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=salesforce works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Salesforce 1

  1. update

    A subset of customers using Lightning Web Runtime sites experienced missing styling and broken page layouts when their pages included rich text or HTML content. Customers were previously informed of this issue via this Trust posting here: https://status.salesforce.com/incidents/20004559. We’ve successfully completed the rollout of the fix. We’ve validated that the issue is now resolved.. We apologize for how this incident may have affected you and your business.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-3d2d9fb2ac

Is Salesforce still down?

No, this incident was resolved 2026-11-04 15:30 UTC. For Salesforce's live state, see https://down.guide/salesforce.

How long did it last?

7d 20h, from 2026-10-27 19:00 UTC to 2026-11-04 15:30 UTC, by the times Salesforce posted.

What was affected?

Salesforce named Communities in can38, usa356, usa358, usa376.

What caused it?

Salesforce hasn't published a root cause. If it does, it shows here.

Where does this come from?

Salesforce's official status page, https://status.salesforce.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.