D-ID Outage History
16 incidents recorded over the last 365 days, 16 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded D-ID Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Potential V4 Agents outage (failed to connect)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… | 22 min | Resolved |
| Aug 31, 2026 | V3 (Clips) Agents Stream Creation ErrorsV3 (Clips) streaming is fully restored and operating normally. | -860 min | Resolved |
| Aug 31, 2026 | V2 (Talks) Agents Streaming OutageV2 (Talks) streaming is fully restored and operating normally. | -783 min | Resolved |
| Aug 11, 2026 | Streaming outage in several avatar typesThe issue affecting Streaming connection failures on several avatar types. has been resolved. Systems are operating normally. We appreciate your patience and apologize for any inconvenience caused. | 10 min | Resolved |
| Aug 9, 2026 | Agent audio not playing for Fluent Clip presentersThe issue affecting specific clip agent presenters has been resolved. | 3 min | Resolved |
| Jun 16, 2026 | Partial Outage in Agents and Talks/Clips StreamingThe issue affecting agents api and streaming is resolved. The issue originated from a scheduled networking maintenance work and is now resolved | 15 min | Resolved |
| Jun 14, 2026 | Outage in Clips (V3 Pro Avatars) Streamer The issue impacting agent streaming of clips presentations has been resolved. | 14 min | Resolved |
| Jun 8, 2026 | Specific avatar sessions failingThe issue affecting Agents sessions has been resolved. Systems are operating normally. We appreciate your patience and apologize for any inconvenience caused. | 1h 49m | Resolved |
| May 5, 2026 | Partial Service OutageThe issue affecting has been resolved. Systems are operating normally. We appreciate your patience and apologize for any inconvenience caused. The issue originated from a cloud provider scheduled upgrade that resulted… | 2h 30m | Resolved |
| Apr 27, 2026 | Partial Outage Expressive AgentsThe issue affecting Expressive agents has been resolved. | 72h 2m | Resolved |
| Apr 21, 2026 | Partial outage on Clips APIThe issue affecting affecting clips creation has been resolved. Systems are operating normally. We appreciate your patience and apologize for any inconvenience caused. | 0 min | Resolved |
| Mar 30, 2026 | Partial outage in Agents V3 streamersThe issue affecting [***brief description of the service or functionality***] has been resolved. Systems are operating normally. We appreciate your patience and apologize for any inconvenience caused. | 1h 56m | Resolved |
| Feb 2, 2026 | Provider Outage: Azure cloud service management issuesThe issue has fully resolved Azure incident ID: FNJ8-VQZ See more: https://azure.status.microsoft/en-us/status/history/ | 12h 27m | Resolved |
| Jan 26, 2026 | Partial outage on embedded agent applicationsBetween Jan 26 at 10:45 PM and Jan 26 at 11:40 PM GMT, we experienced a partial outage in our embedded agent applications | 0 min | Resolved |
| Dec 30, 2025 | Issue with Checkout Prices and Shared Agent LinksThe issue affecting checkout prices and shared agent links has been resolved. All systems are now operating normally | 20 min | Resolved |
| Nov 25, 2025 | Video generation is blocked in certain flowsA critical bug was discovered that prevented video generation in certain Studio flows. The issue has been fixed, and normal functionality is restored. | -20 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next D-ID incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This D-ID Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before D-ID acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single D-ID outage in this window ran 3d, against a mean recovery of 7h 5m. If you depend on D-ID in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.