Delays and failures in video generation
HeyGen video generation is slow or fails in the web app and the API. The delays started at about 02:58 UTC. HeyGen applied a fix and now monitors the recovery. If a video failed, generate it again.
State
Monitoring
Started
Ongoing for
44 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
22 min 50%
Monitoring
22 min 50%
Updates
Times in UTCAs posted by HeyGen
We have applied a fix and video generation in the HeyGen web app and API is recovering; delays that began around 02:58 UTC are easing. We are monitoring closely. If a video failed during this time, please try generating it again.
Since around 02:58 UTC, some videos created in the HeyGen web app and through the API are taking longer than usual to finish, and some may fail. We are investigating. If a video fails, please try generating it again.
HeyGen in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
10
Median duration
1 h 6 min
This incident
33% shorter than the median
Other HeyGen incidents
All incidents
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.
HeyGen·Seedance Outage
Requests that failed during this window were not charged and can be retried now. We'll follow up if anything changes.
HeyGen·Video Agent GET /v3/video-agents/{session_id} 404s on all new sessions
The incident has been 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.
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