Salesforce: Feature Service Disruption: Core Service
Affected components: Core Service1 instance
Timeline of updates
- update
We continue to explore multiple paths to quickly resolve the issue, which include analysing the error logs and additional diagnostic information to determine the potential trigger.
We’ll provide an update upon a significant update, or sooner if additional information becomes available.
- update
At 11: 11 UTC, on September 05, 2026, the team declared an all-clear after validating the services and performing the health checks.
We apologize for how you and your business may have been affected by this incident.
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 this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
5c210453dea1a693…
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-09-05 03:00 UTC, resolved after 8.2 h, 2 update(s).
- Title
- Feature Service Disruption: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004408
Salesforce profileRecent Salesforce incidentsAll outages on September 5, 2026Salesforce in September 2026MarkdownJSON