Voice cache degradation

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 19m it lasted.

  Anything that failed between 2026-02-06 19:25 UTC and 2026-02-06 19:44 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

1. investigatingFeb 6, 2026, 7:25 PM UTC

   We had a voice cache degradation where some generations were not executed and multi-scene videos would have been impacted. The issue began around 3am PST

   provider

2. resolvedFeb 6, 2026, 7:44 PM UTC

   We have identified the problem and put in a correction. Service should be behaving as usual. The cache was in a bad state and some speech audio generations would have been corrupted. This issue began with a deployment on our side at 3am PST. So any videos between then and 1130am PST might have been impacted

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.