HeyGen

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-10 00:37 UTC

   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.

2. resolved 2026-10-11 04:56 UTC

   incident resolved

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-04 22:13 UTC

   We are investigating an issue with Video Agent chats not surfacing and loading

2. resolved 2026-10-04 22:55 UTC

   Identified the rootcause and resolved. Video Agent is back.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-18 23:03 UTC

   We’re investigating an issue affecting some video generation requests. The issue has been identified.

2. resolved 2026-09-19 05:20 UTC

   The incident has been resolved, and the service is now operating normally. Thank you for your patience.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-09-16 18:55 UTC

   Between 8:00AM and 11:00AM PST, Seedance requests failed or timed out. We've deployed a fix and error rates have returned to normal. We're continuing to monitor. Requests that failed during this window were not charged and can be retried now. We'll follow up if anything changes.

2. resolved 2026-09-16 18:57 UTC

   Requests that failed during this window were not charged and can be retried now. We'll follow up if anything changes.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-09 19:25 UTC

   Root cause identified. A fix is rolling out shortly. Some users may also see permission errors on new videos in the dashboard — we're confirming whether that's related.

2. resolved 2026-09-09 23:03 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-20 04:14 UTC

   Team is investigating the cause expect slow downs on services.

2. resolved 2026-08-20 05:20 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. identified 2026-08-17 15:26 UTC

   Several services across HeyGen + LiveAvatar are degraded.

2. resolved 2026-08-17 15:54 UTC

   We identified the source of the performance errors and resolved them. Services are back to normal.

3. monitoring 2026-08-17 16:30 UTC

   Services may be susceptible to temporary degradation in performance. A fix has been identified. We are waiting on GitHub to deploy it to all services

4. resolved 2026-08-17 18:54 UTC

   We have resolved the issue. Services are back to normal

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-13 05:36 UTC

   We are aware of of elevated video translate latency and failure rate, we are working on mitigating it

2. monitoring 2026-08-13 09:51 UTC

   We've identified the cause and are rolling out a fix; some jobs may still see delays while we work through the backlog.

3. resolved 2026-08-13 15:13 UTC

   This issue is resolved

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-30 17:35 UTC

   A spike is slowing down multiple services. We are investigating the issue and expect slow performance until it is fixed.

2. resolved 2026-07-30 18:18 UTC

   The problem has been identified and mitigated.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-24 01:31 UTC

   Flaky sessions. Investigating and mitigating

2. resolved 2026-07-24 03:14 UTC

   Mitigated issue

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-01 19:54 UTC

   Services are experiencing outages. Investigating the root cause.

2. monitoring 2026-07-01 20:02 UTC

   We have identified the issue and reverted the changes. Site is operational now; monitoring for further issues.

3. investigating 2026-07-01 21:01 UTC

   Services are experiencing outages. Triaging in process.

4. investigating 2026-07-01 21:12 UTC

   We have reverted the deployment that caused the issue. The site is operational, and we are investigating the root cause.

5. resolved 2026-07-01 23:33 UTC

   We have resolved the issue. Services are back to normal.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-30 19:28 UTC

   Due to a lack in GPUs available - we're seeing an increase in outages and a degradation in performance.

2. resolved 2026-06-30 20:46 UTC

   We've scaled up number of instances and we're no longer seeing an increase in errors.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-22 20:01 UTC

   We have identified an issue resulting in degraded performance for the web application and API service.

2. monitoring 2026-06-22 20:38 UTC

   Issue has been resolved. Services have recovered, and we are monitoring for continued stability.

3. resolved 2026-06-22 21:10 UTC

   Issue has been resolved.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-18 07:37 UTC

   We have identified and resolved the issue resulting in the temporary outage of the web app and api service errors and are currently monitoring closely to prevent any further issues.

2. resolved 2026-06-18 07:39 UTC

   This issue has been resolved. We saw elevated errors on the web app and api service between 11:45pm PT / 60:45 UTC and 12:10am PT / 07:10 UTC.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-19 22:59 UTC

   We're observed elevated error rates across APP and API. All sessions appear to be affected. We've identified issue and rolling out a fix.

2. resolved 2026-05-19 23:11 UTC

   A hotfix was deployed, error rates are normalized. We're now monitoring.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-29 18:00 UTC

   [https://www.heygenverse.com/a/f2f4f441-aa1a-4ada-9200-aa7d1a79e07f](https://www.heygenverse.com/a/f2f4f441-aa1a-4ada-9200-aa7d1a79e07f "https://www.heygenverse.com/a/f2f4f441-aa1a-4ada-9200-aa7d1a79e07f")

2. resolved 2026-04-29 18:01 UTC

   [https://www.heygenverse.com/a/f2f4f441-aa1a-4ada-9200-aa7d1a79e07f](https://www.heygenverse.com/a/f2f4f441-aa1a-4ada-9200-aa7d1a79e07f "https://www.heygenverse.com/a/f2f4f441-aa1a-4ada-9200-aa7d1a79e07f")

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-25 20:05 UTC

   We identified an issue with our apis and deployed a fix. We are continuing to monitor.

2. resolved 2026-04-26 01:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-14 18:13 UTC

   We have identified an issue that cause the HeyGen platform to be not operational

2. monitoring 2026-04-14 19:01 UTC

   App should be operational now

3. resolved 2026-04-14 19:12 UTC

   The platform is fully operational now.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-13 15:48 UTC

   We have identified an issue where the creation of videos aren't getting processed.

2. investigating 2026-04-13 17:03 UTC

   We have identified an issue where the creation of videos aren't getting processed.

3. monitoring 2026-04-13 19:34 UTC

   The issue should be mostly resolved now. Some workflows might have failed during that period. We're actively monitoring for any more errors.

4. resolved 2026-04-13 21:45 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-01 18:24 UTC

   We've identified an issue in the LiveAvatar database connections. We are looking into a fix right now. It's degrading some sessions from starting.

2. identified 2026-04-01 18:30 UTC

   We're investigating a table lock issue which is degrading service across both LiveAvatar + HeyGen services.

3. monitoring 2026-04-01 18:42 UTC

   We've mitigated the issue - still identifying the root cause of the spike. Estimated that issues started appearing around 30 mins ago.

4. resolved 2026-04-01 18:49 UTC

   Incident is now resolved. Error rates and general system health are back to normal ranges. We will follow up with a root cause analysis once investigation is complete.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-26 07:08 UTC

   Heygen site is slow

2. resolved 2026-03-26 07:22 UTC

   incident is resolved

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-20 22:50 UTC

   We are investigating an issue with our API service. Expect lower availability during this time.

2. resolved 2026-02-20 23:13 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-06 19:25 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

2. resolved 2026-02-06 19:44 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...

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-04 00:34 UTC

   Video Agent service (web & API) is currently degraded

2. identified 2026-02-04 00:56 UTC

   We have identified the cause and are working to implement a fix.

3. resolved 2026-02-04 01:10 UTC

   The issue has been resolved. All services are operating normally.

Excerpts are shortened. Read the full incident on HeyGen's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-02 17:48 UTC

   We are currently investigating an issue with our avatar iv model generation. Until resolved, generation time will be significantly increased.

2. resolved 2026-02-02 19:51 UTC

   The issue has been resolved.

3. resolved 2026-02-02 19:53 UTC

   This issue has been resolved. Avatar IV jobs will be resume normal processing.

Excerpts are shortened. Read the full incident on HeyGen's status page.