Salesforce: Heroku Retroactive Feature Degradation: Cedar Common Runtime
Affected components: Cedar Common Runtime2 instances
Timeline of updates
- update
Customers using Heroku in the Common Runtime may have experienced intermittent dyno disruptions earlier today between 17:50 UTC and 20:24 UTC. The issue has been resolved after we disabled a related service and rolled back a recent change. We’re validating the update in lower environments and will continue monitoring for stability.
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
7cef63b368fb5ed4…
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-02-23 17:50 UTC, resolved after 2.6 h, 1 update(s).
- Title
- Heroku Retroactive Feature Degradation: Cedar Common Runtime
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003722
Salesforce profileRecent Salesforce incidentsAll outages on February 23, 2026Salesforce in February 2026MarkdownJSON