- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on Heroku. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2m it lasted.
Anything that failed between 2026-08-06 16:17 UTC and 2026-08-06 16:19 UTC may need a replay.Subscribe to Heroku's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=heroku works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Heroku 1
- resolved
Between 11:01 UTC on August 6, 2026 and 13:10 UTC on August 6, 2026, we identified a performance issue affecting Heroku release phase deploys. During this time, some customers experienced delayed completion of release phase commands during deploys, with some remaining in an release phase executing state longer than expected. We have confirmed that the issue is resolved. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b30e6cbf0f
Is Heroku still down?
No, this incident was resolved 2026-08-06 16:19 UTC. For Heroku's live state, see https://down.guide/heroku.
How long did it last?
2m, from 2026-08-06 16:17 UTC to 2026-08-06 16:19 UTC, by the times Heroku posted.
What caused it?
Heroku hasn't published a root cause. If it does, it shows here.
Where does this come from?
Heroku's official status page, https://status.heroku.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.