DeepL: Customer are seeing errors reporting "Something went wrong"

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 2026-09-18 04:37 UTC and 2026-09-18 04:37 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.

resolvedSep 18, 2026, 4:37 AM UTC
Affected Services: DeepL Pro - Glossaries, DeepL Pro - Write, DeepL Pro - Document Translation, DeepL Pro - Voice for Conversations, DeepL Pro - Voice for Meetings, Accounts & Login, DeepL Web, DeepL Pro - Translate Started: Fri, 18 Sep 2026 02:30:00 GMT Last Updated: Fri, 18 Sep 2026 04:37:00 GMT Updates: 02:30:00: We are investigating a possible authention problem, leading to sesions expiring and not refreshing correctly. If you experience htis problem, please try logging out from the session and logging in again. Alternatively clear browser cookies, or use try a private (incognito) browser session. 03:15:00: We're investigating the cause of the error messages. Reports indicate this is not affecting the function of the service provided but causing the error message to appear. Clearing the session or the cookies does not resolve the problem, contrary to previous suggestions. 04:13:00: The cause has been identifed with a fix being worked on. The error message is cosmetic and does not affect functionality. A fix is currently being deployed. 04:37:00: A fix for this issue has been deployed. This has been confirmed fixed through tests and corresponding metrics returning to expected levels. Apologies for the inconvienence.
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 2026-09-18 04:37 UTC. For DeepL's live state, see https://down.guide/deepl.

How long did it last?

0m, from 2026-09-18 04:37 UTC to 2026-09-18 04:37 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.