Companies / Salesforce / incidents
Salesforce: Feature Service Disruption: Core Service
Affected components: Core Service3 instances
Timeline of updates
- update
Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.
- update
Upon further investigation, the Salesforce Technology team has determined that the start time of impact is different than initially understood. We have now revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
- update
At 13:21 UTC on January 28, 2026, we began investigating a feature disruption impacting the E360 email service. As a result, users may experience issues where emails appear to send successfully within the application but are not delivered to the recipient's inbox. Our teams are exploring multiple paths to resolution, including a rollback of a recent configuration change. We will provide an update in 60 minutes or sooner as more information becomes available.
- resolved
We’ve confirmed that the solution implemented to mitigate the issue causing the feature disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab). Salesforce profile · Recent Salesforce incidents · Markdown · JSON