Is D-ID API down? › Outage history › Feb 2, 2026

D-ID API outage on Feb 2, 2026: what happened

On Feb 2, 2026, the D-ID status page reported "Provider Outage: Azure cloud service management issues". About 12 hours 27 min: from Feb 2, 2026, 20:30 UTC to Feb 3, 2026, 08:57 UTC, by the official start and resolution times.

D-ID API right now

At our last refresh (Oct 22, 2026, 12:35 UTC) D-ID API was up: All Systems Operational.

Is D-ID API down right now? →
Started
Feb 2, 2026, 20:30 UTC
Resolved
Feb 3, 2026, 08:57 UTC
Duration
12 hours 27 min
Official impact
Critical

The D-ID status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.

What caused the D-ID API outage?

The D-ID status page has not published a cause. When it identified the problem at 20:32 UTC on Feb 2, 2026, it said: "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."

When was it fixed?

The D-ID status page marked it resolved at Feb 3, 2026, 08:57 UTC, 12 hours 27 min after it started. A fix was in place and being monitored from Feb 3, 2026, 07:35 UTC. Its resolution note: "The issue has fully resolved Azure incident ID: FNJ8-VQZ See more: https://azure.status.microsoft/en-us/status/history/"

Timeline of official updates

Every update the D-ID status page posted, oldest first. Times are UTC.

  1. Feb 2, 2026, 20:30 UTC investigating

    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. Feb 2, 2026, 20:32 UTC identified

    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. Feb 2, 2026, 21:34 UTC identified

    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. Feb 3, 2026, 07:35 UTC monitoring

    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. Feb 3, 2026, 08:57 UTC resolved

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

D-ID API outage questions

What caused the D-ID API outage on Feb 2, 2026?

The D-ID status page has not published a cause. When it identified the problem (Feb 2, 2026, 20:32 UTC) it said: "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."

When was the D-ID API outage on Feb 2, 2026 fixed?

The D-ID status page marked it resolved at Feb 3, 2026, 08:57 UTC, 12 hours 27 min after it started. A fix was in place and being monitored from Feb 3, 2026, 07:35 UTC. Its resolution note: "The issue has fully resolved Azure incident ID: FNJ8-VQZ See more: https://azure.status.microsoft/en-us/status/history/"

How long did the D-ID API outage last?

About 12 hours 27 min: from Feb 2, 2026, 20:30 UTC to Feb 3, 2026, 08:57 UTC, by the official start and resolution times.

Was D-ID API completely down?

The D-ID status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.

Other recent D-ID API incidents

Full D-ID API outage history and biggest outages → · Recent outages across all services →

Quotes are the D-ID status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with D-ID API. Times are UTC.