incident fixed and monitoring
none- Started
- Oct 9, 8:37 PM EDT
- Resolved
- Oct 11, 12:56 AM EDT
- Duration
- 28h 19m
HeyGen's updates (2)
- monitoring · Oct 9, 8:37 PM EDT
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.
- resolved · Oct 11, 12:56 AM EDT
incident resolved
What our checks recorded
We checked HeyGen 340 times from HeyGen's start time to its resolution, once every five minutes. Every one of them reached HeyGen's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 100 ms, against 107 ms over the 24 hours before. HeyGen posted the incident at Oct 9, 8:37 PM EDT.
Updates are HeyGen's own words from its status page (status: resolved); we never add an inferred cause.