D
Outage recap · D-ID

D-ID outage — February 2, 2026

On February 2, 2026, D-ID had a reported incident on D-ID's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Provider Outage: Azure cloud service management issues

critical
Started
Feb 2, 3:30 PM EST
Resolved
Feb 3, 3:57 AM EST
Duration
12h 27m

D-ID's updates (5)

  1. investigating · Feb 2, 3:30 PM EST

    We are currently investigating reports of an issue affecting processing performance. Our team is working to identify the root cause while scaling alternative resources to compensate. We will provide an update as soon as more information is available.

  2. identified · Feb 2, 3:32 PM EST

    We have identified the root cause of the issue affecting cloud processing servers. A fix is being implemented. We will continue to provide updates as we make progress.

  3. identified · Feb 2, 4:34 PM EST

    We have identified the root cause of the issue to be a widespread event affecting our Azure US cluster. We will continue to provide updates as we make progress. The service is back to normal operation, creation of **new** agents and avatars is currently still unavailable Azure status page: https://azure.status.microsoft/en-us/status

  4. monitoring · Feb 3, 2:35 AM EST

    Azure has reported a fix has been implemented and we are currently monitoring the results to ensure full recovery. We will confirm once the issue is fully resolved.

  5. resolved · Feb 3, 3:57 AM EST

    The issue has fully resolved Azure incident ID: FNJ8-VQZ See more: https://azure.status.microsoft/en-us/status/history/

Updates are D-ID's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with D-ID. This recap summarizes incidents published on D-ID's official status page.