# Salesforce: Feature Perf Degradation: Communities

> Salesforce status incident “Feature Perf Degradation: Communities” on 2026-10-27: impact minor (vendor’s label), 13 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/salesforce/incidents/20004559
Last updated: 2026-11-04T13:03:00Z

- Impact (vendor’s label): minor
- Status: investigating · edited after publishing
- Started: 2026-10-27 19:00 UTC · Resolved: not resolved · Duration: ongoing
- Updates: 13 · Affected components: Communities, 1016 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004559](https://status.salesforce.com/incidents/20004559)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-11-04 01:42 UTC: 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
- **update** 2026-11-04 02:03 UTC: 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.
- **update** 2026-11-04 02:33 UTC: 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.
- **update** 2026-11-04 03:12 UTC: 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.
- **update** 2026-11-04 04:37 UTC: 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.
- **update** 2026-11-04 05:20 UTC _(edited after publishing)_: 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.
- **update** 2026-11-04 06:29 UTC _(edited after publishing)_: 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.
- **update** 2026-11-04 06:53 UTC: 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.
- **update** 2026-11-04 08:02 UTC: 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.
- **update** 2026-11-04 09:18 UTC: 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.
- **update** 2026-11-04 10:24 UTC: 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.
- **update** 2026-11-04 11:20 UTC: 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.
- **update** 2026-11-04 12:19 UTC: 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.

## Rewindex changes for this incident

- 2026-11-04 02:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/ra83c15e5fee4e6.md)
- 2026-11-04 03:03 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/r5c9e24396edfe3.md)
- 2026-11-04 03:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/recae4dc2f24b82.md)
- 2026-11-04 05:03 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/rc057ec4032a642.md)
- 2026-11-04 05:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/ree8987db577291.md)
- 2026-11-04 06:03 UTC: [Incident silently edited: Feature Perf Degradation: Communities](https://rewindex.com/change/r7c297379a75888.md)
- 2026-11-04 06:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/rf968a7508183b1.md)
- 2026-11-04 07:03 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/r08390f9615acbe.md)
- 2026-11-04 07:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/r6d25bebec8f4b0.md)
- 2026-11-04 08:03 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/r9948ba73f0598a.md)
- 2026-11-04 09:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/r56b742bb7ab346.md)
- 2026-11-04 10:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/rf821fb6417f5f3.md)
- 2026-11-04 11:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/rc9637b84d86218.md)
- 2026-11-04 12:33 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/rff9ef35af7d0fd.md)
- 2026-11-04 13:03 UTC: [Incident updated: Feature Perf Degradation: Communities](https://rewindex.com/change/r87083f83a4f2b4.md)

## Cite this

Status incident (vendor impact label: minor) posted by Salesforce, started 2026-10-27 19:00 UTC, not resolved, 13 update(s); edited after publishing.

- Canonical URL: https://rewindex.com/company/salesforce/incidents/20004559
- Citation: Salesforce, “Feature Perf Degradation: Communities” (2026-10-27 19:00 UTC). Archived by Rewindex: https://rewindex.com/company/salesforce/incidents/20004559 (CC BY 4.0).
- Markdown link: `[Salesforce: Feature Perf Degradation: Communities (2026-10-27)](https://rewindex.com/company/salesforce/incidents/20004559)`


---
Canonical: https://rewindex.com/company/salesforce/incidents/20004559 · Markdown: https://rewindex.com/company/salesforce/incidents/20004559.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004559 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:32:16.468Z