incident fixed and monitoring
incident resolved
The latest update from HeyGen.
State
Resolved
Started
23 d ago
2026-10-10 00:37 UTC
Lasted
28 h 19 min
until 2026-10-11 04:56 UTC
Worst impact
Notice
Timeline
2 updatesMonitoring
28 h 19 min 100%
Updates
Times in UTCAs posted by HeyGen
incident resolved
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.
HeyGen in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
10
Median duration
2 h 22 min
This incident
12× the median
Other HeyGen incidents
All incidents
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.
HeyGen·Increase load on our DB causing service degradation
The issue 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.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.
https://outages.cc/feed.xml?providers=heygen/feed subscribe https://outages.cc/feed.xml?providers=heygenFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane