- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 37of 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 57m it lasted.
Anything that failed between 2026-07-06 13:33 UTC and 2026-07-06 14:30 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
Incident resolved.
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-7b784fc6cf
Is Heroku still down?
No, this incident was resolved 2026-07-06 14:30 UTC. For Heroku's live state, see https://down.guide/heroku.
How long did it last?
57m, from 2026-07-06 13:33 UTC to 2026-07-06 14:30 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.