Heroku: Heroku Service Disruption
Timeline of updates
- resolved
We have successfully applied the fix to all remaining affected customers. Heroku databases and web applications are now fully operational for all customers. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
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
92bb400d41196190…
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-08 03:55 UTC, resolved after 15 h, 1 update(s).
- Title
- Heroku Service Disruption
- Vendor
- Heroku
- Date
- URL
- https://rewindex.com/company/heroku/incidents/2953
Heroku profileRecent Heroku incidentsAll outages on May 8, 2026Heroku in May 2026MarkdownJSON