DeepL: Major Outage

What to do

Check whether your product depends on DeepL. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-12-12 13:20 UTC and 2025-12-12 13:20 UTC may need a replay.
Subscribe to DeepL's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=deepl works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedDec 12, 2025, 1:20 PM UTC
Affected Services: DeepL Pro - Voice for Meetings Started: Fri, 12 Dec 2025 13:12:00 GMT Last Updated: Fri, 12 Dec 2025 13:20:00 GMT Updates: 13:12:00: We're currently experiencing a major disruption. Our team is aware and has started investigating the issue. We’ll provide more details as soon as we have them. 13:18:00: We’re continuing to investigate the disruption. Our engineers are working to identify the cause and restore full functionality. We’ll share another update as soon as we have meaningful progress to report. 13:20:00: The issue has been resolved and systems are operating normally again. We appreciate your patience and apologize for the interruption. A full review is underway to help prevent this from happening again.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is DeepL still down?

No, this incident was resolved 2025-12-12 13:20 UTC. For DeepL's live state, see https://down.guide/deepl.

How long did it last?

0m, from 2025-12-12 13:20 UTC to 2025-12-12 13:20 UTC, by the times DeepL posted.

What caused it?

DeepL hasn't published a root cause. If it does, it shows here.

Where does this come from?

DeepL's official status page, https://status.deepl.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.