Translator page failing to load on custom DeepL subdomains

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-08-14 15:05 UTC and 2026-08-14 15:05 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 14, 2026, 3:05 PM UTC

   Affected Services: DeepL Web Started: Fri, 14 Aug 2026 13:45:06 GMT Last Updated: Fri, 14 Aug 2026 15:05:04 GMT Updates: 13:45:06: We are investigating reports of the translator page failing to load affecting DeepL Web for organisations that access DeepL via a custom subdomain. Users may experience a "Something went wrong" error instead of the translator, and may be unable to log in. The issue began around 10:03 UTC. Our team is actively investigating and we will keep you updated as soon as we have more information. 14:33:51: We have carried out a cache purge for DeepL Web to remove outdated JavaScript and HTML files that may have been cached and were preventing the translator page from loading. We are monitoring recovery. Affected users should now be able to load the translator, and may need to refresh the page. We will keep you updated once we have confirmed full recovery. 15:05:04: The issue affecting DeepL Web has been resolved as of 15:04 UTC. Between 10:03 UTC and 15:04 UTC, users at organisations accessing DeepL via a custom subdomain experienced a "Something went wrong" error instead of the translator page, and in some cases were unable to log in. Root cause: outdated JavaScript and HTML files had been cached and were being served to these users, preventing the translator page from loading. These files have been purged from our cache. All services are now operating normally. If you continue to experience issues, please refresh your page, and contact DeepL Support if the problem persists. We apologise for the disruption.

   provider

Corrections

None so far.

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