DeepL incident

Web errors using DeepL services

Resolved after 1 hour 1 minute, affecting Products (DeepL Free - Document Translation) and Products (DeepL Free - Translate) and 1 more, on August 7, 2026.

resolved Aug 07, 2026, 09:01 AM UTC

We have traced the caused of the issue to a roll back of a prior release, which was performed yesterday. The release was leading to a low level or errors on specific objects, and was therefore reverted. The roll back appears to have left a number of cached objects in our Content Delivery Network which inteferred with the correct operation of our site in customers browsers, which was detected this morning. These objects were cleared from our CDN this morning, which corrected site behaviour. The team are working on improvemnts to our roll-back mechanism which will prevent a similar problem occuring in future.

Started
Aug 07, 2026, 08:00 AM UTC
Resolved
Aug 07, 2026, 09:01 AM UTC
Duration
1h 1m
Detected by Pingoru
Aug 07, 2026, 08:00 AM UTC

Affected components

Products (DeepL Free - Document Translation)Products (DeepL Free - Translate)Products (DeepL Pro - Translate)Products (DeepL Pro - Glossaries)Products (DeepL Pro - Document Translation)Products (DeepL Pro - Write)Products (DeepL Free - Write)Products (DeepL Pro - Voice for Conversations)Products (DeepL Pro - Voice for Meetings)Platform (Accounts & Login)

Update timeline

  1. identified Aug 07, 2026, 08:00 AM UTC

    This morning, we identified a problem causing site failures for customers attempting to use our products. The issue was related to caching of objects following a routine deployment. We have implemented corrective action and are investigating the exact cause and impact of the problem.

  2. resolved Aug 07, 2026, 09:01 AM UTC

    We have traced the caused of the issue to a roll back of a prior release, which was performed yesterday. The release was leading to a low level or errors on specific objects, and was therefore reverted. The roll back appears to have left a number of cached objects in our Content Delivery Network which inteferred with the correct operation of our site in customers browsers, which was detected this morning. These objects were cleared from our CDN this morning, which corrected site behaviour. The team are working on improvemnts to our roll-back mechanism which will prevent a similar problem occuring in future.

Your product runs on more than DeepL

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →