Resolved after 21 minutes, affecting API (DeepL Free - API (EU)) and Products (DeepL Free - Document Translation) and 1 more, on August 18, 2026.
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.
Affected components
Update timeline
- investigating Aug 18, 2026, 10:20 PM UTC
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.
- resolved Aug 18, 2026, 10:41 PM UTC
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.
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.
Amazon Web Services