Heroku: Heroku Feature Disruption
Timeline of updates
- resolved
Upon further investigation, we've determined that the start time of impact is different than initially understood. We've 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.
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
2df1c6cede42881f…
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-05-05 14:57 UTC, resolved after 3.1 h, 1 update(s).
- Title
- Heroku Feature Disruption
- Vendor
- Heroku
- Date
- URL
- https://rewindex.com/company/heroku/incidents/2952
Heroku profileRecent Heroku incidentsAll outages on May 5, 2026Heroku in May 2026MarkdownJSON