API Service Outage
The HeyGen API service had a short outage. HeyGen reports that the incident is resolved and that it lasted 3 minutes. HeyGen estimates around 5 minutes of degraded service.
State
Resolved
Started
Lasted
3 min
Worst impact
Degraded
Timeline
2 updatesMonitoring
3 min 100%
Updates
Times in UTCAs posted by HeyGen
We estimate around 5 minutes of degraded service occurred.
A misconfiguration resulted in a short outage.
HeyGen in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
11
Median duration
3 h 28 min
This incident
99% shorter than the median
Other HeyGen incidents
All incidents
HeyGen·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.

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.
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