Heroku: Heroku Retroactive Service Disruption
Timeline of updates
- resolved
We noted an issue that impacted Heroku Platform API services in all regions. Customers may have experienced broken pipeline API calls to ‘pipelines/:id/latest-builds’, and issues viewing the pipeline dashboard. We confirmed this incident was due to a recently deployed change, and have reverted this change to resolve the issue.
We will continue to monitor the environment to ensure stability and prevent a recurrence. We will also thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and any 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
6ce55f68c3a1aaf5…
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-06-19 18:47 UTC, resolved after 23 min, 1 update(s).
- Title
- Heroku Retroactive Service Disruption
- Vendor
- Heroku
- Date
- URL
- https://rewindex.com/company/heroku/incidents/2957
Heroku profileRecent Heroku incidentsAll outages on June 19, 2026Heroku in June 2026MarkdownJSON