Translator page failing to load on custom DeepL subdomains

Update timeline

1. identified Aug 14, 2026, 01:45 PM UTC

   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.

2. investigating Aug 14, 2026, 02:33 PM UTC

   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.

3. resolved Aug 14, 2026, 03:05 PM UTC

   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.