Is DeepL Down?
Reachable from all 8 checked regions
Average response time: 254ms
Last checked · checks run every 6 hours
Official status page: https://status.deepl.com
DeepL uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 31 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
31-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What DeepL does
DeepL is a machine translation service covering more than 100 languages, offered as a web translator, desktop and mobile apps, browser extensions and an API. Alongside the translator it sells Write, Voice and document translation, plus glossaries and terminology rules for consistent wording. DeepL says more than 200,000 businesses use it, many through the API rather than the website.
What an outage looks like
Translations return empty or hang with the spinner running, and the site or app reports a generic error without naming a cause. API integrations see requests time out or return server errors, which in most applications surfaces as untranslated source text rather than as a visible failure. Document translation jobs stall in the queue, and glossary lookups can fail while plain translation still works.
What to do about it
Check status.deepl.com for DeepL's own report. If you are calling the API, separate an outage from a quota or rate-limit rejection first, because both stop translations and only one is DeepL's fault; the error code your client receives distinguishes them. Document jobs already submitted usually complete once service returns, so resubmitting the same file mainly consumes character allowance twice.
Is it down for everyone, or just you?
If this page says DeepL is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
DeepL outage FAQ
Is DeepL down for everyone or just me?
Does a DeepL outage affect the API and the website equally?
Will my document translation finish if DeepL goes down mid-job?
Do my glossaries and saved settings survive an outage?
How we measure this
- We request DeepL's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where DeepL publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when DeepL goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring