Salesforce: Feature Perf Degradation: Communities
Affected components: Communities19 instances
Timeline of updates
- update
GovCloud customers are experiencing 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. Customers were previously informed of this issue via this Trust posting here: https://status.salesforce.com/incidents/20004559 (opens in new tab). We’ve determined that a separate fix is required to resolve the issue for your instance Deployment is due to begin in 6 hours due to additional testing that is required. We'll provide the next update in 6 hours, or sooner if we have new information.
- update
The release is progressing through testing and build steps, and we’ll deploy it to GovCloud instances next. We expect this to take several hours, and we’ll provide an update in six hours or sooner if additional information becomes available.
- update
We're continuing the build and testing work we need to finish before we deploy the release to GovCloud instances. We're prioritizing the remaining steps to make sure the release is ready for deployment. We'll provide another update in six hours or sooner if additional information becomes available. We apologize for the continued inconvenience.
- update
We've completed testing of the fix and started deploying it to the affected sandbox instances. Once we validate the sandbox deployments, we'll deploy to production instances.
We'll provide an update as soon as the deployment is completed or additional information becomes available. We apologize for the continued inconvenience.
- 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.
Changes Rewindex caught on this incident
- Incident updated: Feature Perf Degradation: Communities
- Incident updated: Feature Perf Degradation: Communities
- Incident updated: Feature Perf Degradation: Communities
- Incident updated: Feature Perf Degradation: Communities
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-04 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
5770ded40d114a82…Version 2 captured
In the 2026-11-04 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
83cc8544570bada9…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-10-27 19:00 UTC, resolved after 9 d, 5 update(s); edited after publishing.
- Title
- Feature Perf Degradation: Communities
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004561
Salesforce profileRecent Salesforce incidentsAll outages on October 27, 2026Salesforce in October 2026MarkdownJSON