- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 27of 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 1h 3m it lasted.
Anything that failed between 2026-02-23 22:28 UTC and 2026-02-23 23:31 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
Customers using Heroku in the Common Runtime may have experienced intermittent dyno disruptions earlier today between 17:50 UTC and 20:24 UTC. The issue has been resolved after we disabled a related service and rolled back a recent change. We’re validating the update in lower environments and will continue monitoring for stability.
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-0635c48ba9
Is Heroku still down?
No, this incident was resolved 2026-02-23 23:31 UTC. For Heroku's live state, see https://down.guide/heroku.
How long did it last?
1h 3m, from 2026-02-23 22:28 UTC to 2026-02-23 23:31 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.