# Salesforce: Feature Perf Degradation: Core Service

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-02-23 12:00 UTC · Resolved: 2026-02-26 08:09 UTC · Duration: 3 d
- Updates: 7 · Affected components: Core Service, 784 instances
- [Vendor status page: https://status.salesforce.com/incidents/20003725](https://status.salesforce.com/incidents/20003725)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-02-25 03:49 UTC: Starting at 12:00 UTC on February 23, 2026, we received alerts affecting Platform Events and Change Data Capture across multiple instances. Some customers may notice that certain event notifications are delayed, missing, or appear out of order. We're currently investigating the cause of these interruptions, including possible connection issues, and are working on a fix. This may include reverting to a recent change update. We'll share another update within 30 minutes, or sooner if we have more information.
- **update** 2026-02-25 03:49 UTC: We’re addressing the issue by increasing monitoring to identify the source of connection failures, and rolling back ‌recent releases that may be the likely trigger.We’re preparing a fix forward, which will be tested prior to a wider rollout. We'll share another update within 60 minutes, or sooner if we have more information.
- **update** 2026-02-25 03:50 UTC: We’re working on implementing a fix that we believe will resolve the impact to customers. However, we’ll share another update as soon as we have more information or once service is fully restored.
- **update** 2026-02-25 07:47 UTC: We’ve deployed the fix in a test environment and validated it with positive initial results. We're continuing to monitor the fix under varied traffic conditions and will begin a fleet-wide rollout today using a staggered deployment to all impacted instances. We’ll provide the next update once fleetwide deployment begins, or sooner as  additional information is available.
- **update** 2026-02-25 15:41 UTC: The fleet-wide rollout began at 10:30 UTC and the rollout will continue in a staggered manner outside customer business hours.  We'll provide an update as and when we have additional information.
- **update** 2026-02-25 19:20 UTC: 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** 2026-02-26 11:00 UTC: The fleet-wide rollout has been successfully completed across all impacted instances, and we have confirmed that event processing and delivery are performing as expected. Customers will receive an additional resolved notification specific to their instance. These follow-up communications will provide resolution timing specific to their instance. We apologize for any inconvenience caused during this incident.


---
Canonical: https://rewindex.com/company/salesforce/incidents/20003725 · Markdown: https://rewindex.com/company/salesforce/incidents/20003725.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20003725 · Generated 2026-10-18T11:26:54.239Z