Heroku: Heroku Retroactive Feature Disruption
Timeline of updates
- resolved
The issue is now resolved.
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-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
106be7b904c682ec…
Impact, status and times are the vendor’s own, as last archived. View on status.heroku.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Heroku, started 2026-04-29 15:49 UTC, resolved after 0 min, 1 update(s).
- Title
- Heroku Retroactive Feature Disruption
- Vendor
- Heroku
- Date
- URL
- https://rewindex.com/company/heroku/incidents/2951
Heroku profileRecent Heroku incidentsAll outages on April 29, 2026Heroku in April 2026MarkdownJSON