- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on HeyGen. 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 1d 4h it lasted.
Anything that failed between 2026-10-10 00:37 UTC and 2026-10-11 04:56 UTC may need a replay.Subscribe to HeyGen's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=heygen works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from HeyGen 2
- monitoring
Around 4,000 signed-in users received this error, 2,000 of which are not able to sign in at the end of the session. 800 of those 2,000 are returning users, and 1,200 of them are new users.
provider
- 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-1b6085527d
Is HeyGen still down?
No, this incident was resolved 2026-10-11 04:56 UTC. For HeyGen's live state, see https://down.guide/heygen.
How long did it last?
1d 4h, from 2026-10-10 00:37 UTC to 2026-10-11 04:56 UTC, by the times HeyGen posted.
What caused it?
HeyGen hasn't published a root cause. If it does, it shows here.
Where does this come from?
HeyGen's official status page, https://status.heygen.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.