outages.live
Live
HeyGen logo

HeyGen

HeyGen is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

8

Days with an incident

10

Median duration

2 h 22 min

Longest incident

28 h 19 min

Components

6
https://www.heygen.com Operational
90 days agoNo incidentsToday
https://app.heygen.com Operational
90 days agoNo incidentsToday
https://api.heygen.com Operational
90 days agoNo incidentsToday
https://www.liveavatar.com Operational
90 days agoNo incidentsToday
https://app.liveavatar.com Operational
90 days agoNo incidentsToday
https://api.liveavatar.com Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 10, 2026

Duration28 h 19 min00:37 to 04:56incident fixed and monitoringNotice

incident resolved

Oct 4, 2026

Duration42 min22:13 to 22:55Video Agent OutageNotice

Identified the rootcause and resolved. Video Agent is back.

Sep 18, 2026

Duration6 h 17 min23:03 to 05:20HeyGen Video Workflow FailuresDegraded

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

Sep 16, 2026

Duration2 min18:55 to 18:57Seedance OutagePartial outage

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

Sep 9, 2026

Duration3 h 39 min19:25 to 23:03Video Agent GET /v3/video-agents/{session_id} 404s on all new sessionsPartial outage

The incident has been resolved.

Aug 20, 2026

Duration1 h 6 min04:14 to 05:20Increase load on our DB causing service degradationNotice

The issue has been resolved.

Aug 17, 2026

Duration29 min15:26 to 15:54Degraded ServiceDegraded

We have resolved the issue. Services are back to normal

Aug 13, 2026

Duration9 h 37 min05:36 to 15:13Elevated video translate latency and failureNotice

This issue is resolved

Follow HeyGen

Your coding agent knows when HeyGen is down, and tells you when a failure is theirs, not yours. You can also get HeyGen incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "heygen" and tell me if HeyGen has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=heygen
Slack
/feed subscribe https://outages.cc/feed.xml?providers=heygen

Go from tracking outages to fixing production issues with Polylane.

Try Polylane