- Level
- confirmed
- Worst impact
- Degraded
- Components
- Communities
- Regions
- are12, aus84, che6, che12, che16, che18, che28, che30, cs115, cs116, cs137, cs148, cs151, cs152, cs236, cs251, cs258, cs261, cs277, cs331, deu36, deu38, deu52, deu54, deu56, deu58, deu60, deu66, deu68, deu70, deu72, deu74, deu76, deu78, deu84, deu86, deu90, deu92, deu94, deu96, deu100, deu102, deu106, deu108, deu110, deu112, deu118, deu120, deu122, deu124, deu126, deu128, deu130, deu132, deu152, eu49, eu54, eu55, fra32, fra34, fra36, fra42, fra44, fra46, fra48, fra50, fra52, fra54, fra56, fra62, fra64, fra66, fra70, fra74, fra76, fra78, fra80, fra84, fra86, fra88, fra90, fra100, fra104, gbr34, gbr36, gbr38, gbr46, gbr48, gbr50, gbr52, gbr54, gbr56, gbr58, gbr64, gbr66, gbr68, gbr72, gbr74, gbr76, gbr78, gbr80, gbr82, gbr84, gbr86, gbr88, gbr94, gbr96, gbr98, gbr100, gbr102, gbr112, gbr116, gbr118, gbr120, gbr122, gbr124, gbr140, gbr148, ind54s, ind90, isr10, ita6, ita8, ita10, ita12, ita14, ita16, ita18, ita24, ita26, ita28, ita30, ita34, ita36, ita38, ita42, ita54, na223, na224, na231, na233, na234, na235, na236, na237, na239, na240, na243, na246, na248, na249, na251, na253, na254, swe8, swe10, swe12, swe14, swe16, swe18, swe20, swe22, swe24, swe26, swe32, swe34, swe36, swe38, swe40, swe42, swe46, swe48, swe50, swe52, swe54, swe56, swe58, swe62, swe64, swe66, swe68, swe70, swe72, swe74, swe76, swe78, swe80, swe82, swe84, swe98, swe106, swe108, swe112, swe114, swe118, swe122, swe124, swe126, usa194s, usa474, usa1026, usa1062, usa1228s, usa1230, usa1232, usa1434
- Down Index
- 43of 100
What to do
Check whether you use Salesforce Communities in are12, aus84, che6, che12. 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 8d 10h it lasted.
Anything that failed between 2026-10-27 19:00 UTC and 2026-11-05 05:00 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 26
- update
We're aware of an issue affecting Lightning Web Runtime sites that use rich text or HTML content. A subset of customers may see missing styling and broken layouts, on their site pages. The issue appears related to a recent update to a service. We're exploring multiple paths to resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available
provider
- update
We've identified the cause as a recent update to a site component that changes how rich text and HTML content displays. We’ve reproduced the issue and confirmed it can affect any Lightning Web Runtime site on the current release. We are preparing and validating a configuration change that will revert the recent update. We will deploy this fix as soon as we are able to verify that it restores services to users. We'll provide an update in 30 minutes or sooner if additional information becomes available, and apologize for any inconvenience this issue may be causing.
provider
- update
We continue to test and validate the configuration change to ensure this restores services to users. We’re also evaluating whether a configuration change can correct the display while also keeping the current update. We'll provide an update in 30 minutes or sooner if additional information becomes available, and apologize for any inconvenience this issue may be causing.
provider
- update
We’re building a fix for the formatting issue rather than reverting the earlier change, following further investigation and testing. We’re bringing in additional support to develop this fix. We don’t yet have a timeframe for developing and testing this. Additionally, customers should not republish their sites while work is ongoing. We’re developing a Knowledge Article to help customers in the short term. We will provide the next update as soon as we can clarify a timeframe for the development of the fix forward, or if additional information becomes available. We apologize for any inconvenience this issue may be causing.
provider
- update
Multiple swimlanes are again being investigated. The fix forward is prioritized, however, with deeper understanding of the issue, a release to revert the earlier change is once again being pursued as the quickest way to restore services for customers. We encourage customers not to republish their sites while work is ongoing. We'll provide an update as soon as additional information becomes available, and apologize for any inconvenience this issue may be causing.
provider
- update
We have developed a fix to revert the earlier change and are completing the prerequisite tasks for deployment. For additional details, please refer to the Known Issue here :https://sfdc.co/kq6uu2 We'll provide an update in 60 minutes or sooner if additional information becomes available, and apologize for any inconvenience this issue may be causing.
provider
- update
We’re validating the fix in a test environment before deploying it to production. In parallel, we continue to prepare the deployment to restore the correct display of affected Lightning Web Runtime sites. We continue to advise customers not to republish their sites while work is ongoing. We'll provide an update in 60 minutes or sooner if additional information becomes available, and apologize for any inconvenience this issue may be causing.
provider
- update
Following further investigation, we have confirmed that the USA9014 instance is not impacted by the formatting issue affecting Lightning Web Runtime sites. We continue to investigate and address the issue across affected instances. We'll provide an update in 60 minutes or sooner if additional information becomes available, and apologize for any inconvenience this issue may be causing.
provider
- update
We are currently building the fix and will begin validating it in a test environment once the build is complete. We continue to prioritize deploying the fix to production instances to restore the correct display of affected Lightning Web Runtime sites. We'll provide an update in 60 minutes or sooner if additional information becomes available, and apologize for any inconvenience this issue may be causing.
provider
- update
We continue to work on resolving an issue impacting Lightning Web Runtime (LWR) sites within Experience Cloud on Core Hyperforce. This issue is causing missing styling and broken layouts on customer-facing pages that use rich text or HTML content, including tables. We have confirmed in a staging environment that reverting an earlier change restores the expected page rendering, validation checks and builds are in progress. Once the build is complete, deployment will begin and is expected to take at least one to two hours. We are also working on a long-term solution to prevent this issue from recurring. In the meantime, we ask that you avoid republishing your sites while the fix is being deployed. We’ll provide another update in 60 minutes or sooner if new information becomes available. We apologize for the disruption and appreciate your patience as we work to restore normal functionality.
provider
- update
We’ve completed the required production builds and are now preparing to roll out the fix across the impacted instances in phases. We’re also continuing work on a long term solution to help prevent the issue from recurring. We’ll provide another update in 60 minutes or sooner if new information becomes available. We apologize for the disruption and appreciate your patience as we work to restore normal functionality.
provider
- update
We've started rolling out the fix across the impacted instances in phases and are closely monitoring the progress to ensure everything is working as expected. In parallel, we continue to validate a long term solution to help prevent the issue from recurring. We’ll provide another update in 60 minutes or sooner if new information becomes available.
provider
- update
We're still rolling out the fix across the impacted instances. We're doing this in stages and will let customers know when their specific instance has received it. We're also still testing a long-term solution to help ensure the issue doesn't recur. We'll provide another update in 60 minutes or sooner if new information becomes available.
provider
- update
The fix has completed across a number of instances and customers on those instances have been informed that they are now no longer impacted. We’re continuing to monitor the process of the fix rollout. We’ll provide an update in two hours or sooner if additional information becomes available.
provider
- update
The rollout of the fix is progressing across affected instances, and we're continuing to monitor it carefully. We're notifying customers separately as their instances receive the fix. We'll provide an update in two hours or sooner if additional information becomes available.
provider
- update
We've completed the fix on a number of impacted instances, and we're continuing to roll out the fix and are monitoring the progress closely. We're notifying customers separately as their instances receive the fix. We'll provide an update in two hours or sooner if additional information becomes available.
provider
- update
We’re approximately 39% complete with the rollout and are continuing to monitor progress closely. We’re notifying customers separately as their instances receive the fix. We’ll provide an update in two hours or sooner if additional information becomes available.
provider
- update
The fix has completed across a number of instances and customers on those instances have been informed that they are now no longer impacted. We’re continuing to monitor the process of the fix rollout. We’ll provide an update in two hours or sooner if additional information becomes available.
provider
- update
We’re approximately 75% complete with the rollout and are continuing to monitor progress closely. We’re notifying customers separately as their instances receive the fix. We’ll provide an update in two hours or sooner if additional information becomes available.
provider
- update
We've completed the fix on a number of impacted instances, and we're continuing to roll out the fix and are monitoring the progress closely. We're notifying customers separately as their instances receive the fix. We'll provide an update in two hours or sooner if additional information becomes available.
provider
- update
We've completed the fix on a number of impacted instances, and we're continuing to roll out the fix and are monitoring the progress closely. We're notifying customers separately as their instances receive the fix. We'll provide an update in two hours or sooner if additional information becomes available.
provider
- update
We've completed the fix on a number of impacted instances, and we're continuing to roll out the fix and are monitoring the progress closely. We're notifying customers separately as their instances receive the fix. We'll provide an update in two hours or sooner if additional information becomes available.
provider
- update
We’re approximately 90% complete with the rollout and are continuing to monitor progress closely. We’re notifying customers separately as their instances receive the fix. We’ll provide an update in two hours or sooner if additional information becomes available. Additional information: Additional information is available in our Known Issue: https://sfdc.co/kq6uu2
provider
- update
We have completed the rollout for most of the impacted instances and continue to monitor the progress closely. We’re notifying customers separately as their instances receive the fix. We’ll provide an update in two hours or sooner if additional information becomes available. Additional information: Additional information is available in our Known Issue: https://sfdc.co/kq6uu2
provider
- update
We have completed the rollout for most of the impacted instances and continue to monitor the progress closely. We’re notifying customers separately as their instances receive the fix. We’ll provide an update in two hours or sooner if additional information becomes available. Additional information: Additional information is available in our Known Issue: https://sfdc.co/kq6uu2
provider
- update
We have successfully completed the deployment of the fix across all affected instances, and the issue resulting in broken page layouts and missing styling on Lightning Web Runtime (LWR) sites has been resolved. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
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-2035e5ec55
Is Salesforce still down?
No, this incident was resolved 2026-11-05 05:00 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
8d 10h, from 2026-10-27 19:00 UTC to 2026-11-05 05:00 UTC, by the times Salesforce posted.
What was affected?
Salesforce named Communities in are12, aus84, che6, che12.
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.