Degraded video generation
HeyGen video generation pipelines had degraded performance. HeyGen reports that the incident is resolved, and it lasted 81 minutes. All systems are back to normal.
State
Resolved
Started
Lasted
1 h 21 min
Worst impact
Notice
Timeline
3 updatesIdentified
4 min 4%
Monitoring
1 h 17 min 96%
Updates
Times in UTCAs posted by HeyGen
All systems back to normal.
We have successfully mitigated the issue. Video generation services should return to normal soon. We’ll continue to monitor.
We’ve identified the root cause behind a degradation in our video generation pipelines.
HeyGen in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
10
Median duration
3 h 34 min
This incident
62% shorter than the median
Other HeyGen incidents
All incidents
HeyGen·Degraded Performance
HeyGen reported degraded performance that affected the HeyGen web app and API. HeyGen identified the root cause and resolved the issue. The outage lasted about 3 hours and 28 minutes.

HeyGen·Delays and failures in video generation
HeyGen video generation in the web app and the API had delays and some failures. LiveAvatar creation was also slow. HeyGen reports that the issue is resolved and all services are back to normal. The incident lasted about 3 hours and 45 minutes.

HeyGen·incident fixed and monitoring
incident resolved

HeyGen·Video Agent Outage
Identified the rootcause and resolved. Video Agent is back.

HeyGen·HeyGen Video Workflow Failures
The incident has been resolved, and the service is now operating normally. Thank you for your patience.
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.
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.live/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.
https://outages.live/feed.xml?providers=heygen/feed subscribe https://outages.live/feed.xml?providers=heygenFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane