Outage recap · DeepL

DeepL outage — May 13, 2025

On May 13, 2025, DeepL had 2 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.

Partial Outage – US API Usage Endpoints

none
Started
May 13, 5:14 AM EDT
Resolved
May 12, 4:07 PM EDT
Duration
—

DeepL's updates (1)

  1. resolved · May 12, 4:07 PM EDT

    On May 12, 2025, between 20:34 and 21:07 UTC, a misconfiguration was deployed to our API infrastructure, causing requests to the /v2/usage and /v1/usage endpoints on api-us.deepl.com to fail with HTTP 500 errors. As a result, the overall API success rate temporarily dropped to around 80%. The issue was identified and fully resolved by rolling back the misconfiguration at 21:07 UTC. We sincerely apologize for any inconvenience this may have caused.

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 – Account Area User List & Analytics

major
Started
May 13, 5:29 AM EDT
Resolved
May 14, 4:58 AM EDT
Duration
23h 28m

DeepL's updates (4)

  1. investigating · May 13, 5:29 AM EDT

    We are currently investigating this issue.

  2. investigating · May 13, 6:18 AM EDT

    We are currently investigating an issue causing timeouts when loading the user list and analytics data in the account area. This affects the ability to view and manage users, as well as access usage analytics. Our team has identified the problem and is actively working on a fix. We will provide updates as soon as more information becomes available. We apologize for the inconvenience and thank you for your patience.

  3. resolved · May 14, 4:58 AM EDT

    This incident has been resolved.

  4. postmortem · May 14, 5:22 AM EDT

    From May 7 to May 13, 2025, users experienced timeouts when accessing the user list and analytics in the account area. The issue was caused by performance regressions in one of our backend systems following a recent upgrade, which led to slow responses and request timeouts. We have applied mitigations and are working on further improvements to prevent similar issues after future upgrades. We apologize for the inconvenience and appreciate your patience.

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.