Elevated error rates

What to do

• Check whether you use DeepL in eu, us. 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-08-18 22:41 UTC and 2026-08-18 22:41 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.

Updates from DeepL 1

1. resolvedAug 18, 2026, 10:41 PM UTC

   Affected Services: DeepL Free - Document Translation, DeepL Pro - API (JP), DeepL Apps, DeepL Web, Accounts & Login, DeepL Pro - API (US), DeepL Pro - Voice for Meetings, DeepL Pro - Voice for Conversations, DeepL Free - Write, DeepL Pro - Write, DeepL Pro - Document Translation, DeepL Pro - API (EU), DeepL Pro - Glossaries, DeepL Pro - Translate, DeepL Free - Translate, DeepL Free - API (EU) Started: Tue, 18 Aug 2026 22:20:00 GMT Last Updated: Tue, 18 Aug 2026 22:41:00 GMT Updates: 22:20:00: We are investigating elevated error across our servcies. Some users may be getting error messages. We have identified the cause and are working on a fix. A further update will follow shortly. 22:41:00: We found the issue and resolved it.   The cause was a routing issue on part of our external load-balancing layer, which stopped directing traffic to the meetings service following a routine deployment. The service itself remained healthy throughout, and customers on internal network connections were not affected. We restored correct routing across all affected load balancers and have confirmed that traffic and error rates are back to normal. We are reviewing the deployment process to prevent a recurrence.

   provider

Corrections

None so far.

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