Outage recap · DeepL

DeepL outage — May 19, 2025

On May 19, 2025, DeepL had 3 reported incidents on DeepL's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Elevated Error rates on DeepL Pro Services

minor
Started
May 19, 2:07 AM EDT
Resolved
May 19, 2:25 AM EDT
Duration
18 min

DeepL's updates (3)

  1. investigating · May 19, 2:07 AM EDT

    We are currently investigating this issue.

  2. monitoring · May 19, 2:16 AM EDT

    A fix has been implemented and we are monitoring the results.

  3. resolved · May 19, 2:25 AM EDT

    This incident has been resolved.

Updates are DeepL's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Degraded performance on DeepL Pro

minor
Started
May 19, 5:09 AM EDT
Resolved
May 19, 5:29 AM EDT
Duration
20 min

DeepL's updates (2)

  1. investigating · May 19, 5:09 AM EDT

    We are investigating this issue.<br><br><b>Affected Services:</b> Write<br><b>Additional Info:</b> We are investigating issues with DeepL Write in Spanish

  2. resolved · May 19, 5:29 AM EDT

    This incident has been resolved.

Updates are DeepL's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Partial outage on DeepL Voice for Meetings

major
Started
May 19, 8:40 AM EDT
Resolved
May 19, 9:48 AM EDT
Duration
1h 8m

DeepL's updates (4)

  1. investigating · May 19, 8:40 AM EDT

    We are investigating this issue.<br><br><b>Affected Services:</b> Voice<br><b>Additional Info:</b> We are investigating problems with DeepL Voice

  2. identified · May 19, 9:40 AM EDT

    The issue has been identified and a fix is being implemented.

  3. resolved · May 19, 9:48 AM EDT

    This incident has been resolved.

  4. postmortem · May 19, 10:05 AM EDT

    A networking error temporarily prevented our bot from retrieving the list of users in a Microsoft Teams call from 12:40 UTC to 13:45, which disrupted its ability to operate as expected. The issue has since been identified and resolved. We are currently reviewing and hardening our network and bot configurations to prevent similar disruptions in the future.

Updates are DeepL's own words from its status page (status: postmortem); we never add an inferred cause. The vendor's incident page ↗

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