Outage recap · DeepL

DeepL outage — March 11, 2025

On March 11, 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 on DeepL Free, DeepL Pro, DeepL Free API, DeepL Pro API

major
Started
Mar 11, 10:11 AM EDT
Resolved
Mar 11, 10:33 AM EDT
Duration
23 min

DeepL's updates (5)

  1. investigating · Mar 11, 10:11 AM EDT

    We are investigating this issue.<br><br><b>Affected Services:</b> Login SSO<br><b>Affected Clients:</b> Website

  2. monitoring · Mar 11, 10:27 AM EDT

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

  3. monitoring · Mar 11, 10:33 AM EDT

    We are continuing to monitor for any further issues.

  4. resolved · Mar 11, 10:33 AM EDT

    This incident has been resolved.

  5. postmortem · Mar 12, 9:49 AM EDT

    On 11 March, between 14:06 UTC and 14:26 UTC, a network misconfiguration inadvertently caused an outage that affected customers' ability to log in to our services. Our dedicated network operations team quickly identified the problem and worked efficiently to restore access, successfully bringing all of our services back to normal operation. Other features remained fully functional during this time. In order to reduce the risk of similar incidents occurring in the future and to strengthen the reliability of our network infrastructure, we are putting additional measures in place. We would like to sincerely apologise for any inconvenience this may have caused.

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

Partial outage on DeepL Pro, DeepL Pro API

major
Started
Mar 11, 10:52 AM EDT
Resolved
Mar 11, 11:11 AM EDT
Duration
18 min

DeepL's updates (4)

  1. investigating · Mar 11, 10:52 AM EDT

    We are investigating this issue.<br><br><b>Affected Services:</b> Glossary<br><b>Affected Clients:</b> Website, Windows App, MacOS App, Android App, iOS App, Chrome Plugin, Edge Plugin

  2. monitoring · Mar 11, 10:59 AM EDT

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

  3. resolved · Mar 11, 11:11 AM EDT

    This incident has been resolved.

  4. postmortem · Mar 12, 9:39 AM EDT

    On March 11, from 02:40 UTC to 02:55 UTC, a routing misconfiguration caused an internal outage that affected customers ability to use of glossary features properly. Our network operations team quickly identified the root cause and restored the affected services, successfully bringing everything back online and resuming normal operations. Importantly, translations were not impacted. To prevent similar disruptions in the future and enhance the stability of our network infrastructure, we are implementing additional safeguards. We sincerely apologise for any inconvenience this may have caused during this time.

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.