Potential V4 Agents outage (failed to connect)
critical- Started
- Nov 3, 4:52 AM EST
- Resolved
- Nov 3, 5:15 AM EST
- Duration
- 22 min
D-ID's updates (2)
- investigating · Nov 3, 4:52 AM EST
We are currently investigating reports of an issue affecting users ability to connect with v4 agents . Our team is working to identify the root cause. We will provide an update as soon as more information is available.
- resolved · Nov 3, 5:15 AM EST
The issue affecting V4 agents has been resolved. A bad configuration prevent the agents from connecting to new sessions - after fixing the configuration systems are operating normally. We appreciate your patience and apologize for any inconvenience caused.
What our checks recorded
We checked D-ID 4 times from D-ID's start time to its resolution, once every five minutes. Every one of them reached D-ID'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 134 ms, against 532 ms over the 24 hours before. D-ID posted the incident at Nov 3, 4:52 AM EST.
Updates are D-ID's own words from its status page (status: resolved); we never add an inferred cause.