Is DeepL Down?

No — DeepL is up

Reachable from all 8 checked regions

Average response time: 366ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.deepl.com

DeepL uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

335ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability 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.

arn

74ms

DNS 0ms TCP 1ms TLS 7ms TTFB 65ms

bom

873ms

DNS 0ms TCP 4ms TLS 12ms TTFB 857ms

cdg

245ms

DNS 0ms TCP 2ms TLS 7ms TTFB 200ms

dfw

216ms

DNS 0ms TCP 2ms TLS 10ms TTFB 206ms

ewr

283ms

DNS 0ms TCP 2ms TLS 6ms TTFB 273ms

fra

181ms

DNS 0ms TCP 1ms TLS 8ms TTFB 174ms

gru

451ms

DNS 0ms TCP 2ms TLS 8ms TTFB 440ms

iad

221ms

DNS 0ms TCP 2ms TLS 7ms TTFB 211ms

jnb

460ms

DNS 0ms TCP 0ms TLS 6ms TTFB 453ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

DeepL outage FAQ

Is DeepL down for everyone or just me?

Check status.deepl.com first. If it reports no incident, the next most likely causes are a browser extension conflict, a corporate proxy blocking the API endpoint, or an exhausted character quota on your plan. API users should confirm the error code returned rather than the symptom, since a rejected request and an unreachable service both leave source text untranslated in the application.

Does a DeepL outage affect the API and the website equally?

Not always. The web translator, the apps and the API are separate surfaces, and integrations frequently keep failing after the website recovers, or the reverse. If your application has stopped translating, test the same text on deepl.com before assuming a platform-wide fault; a working website with a failing API points at your credentials, quota or endpoint rather than at DeepL.

Will my document translation finish if DeepL goes down mid-job?

Document translation is a queued job rather than a live request, so a job already accepted normally completes once service returns. The failure mode to avoid is resubmitting: each submission consumes character allowance against your plan, so a duplicate costs twice for one result. Wait for the original job to report before uploading the file again.

Do my glossaries and saved settings survive an outage?

Glossaries and terminology rules are stored by DeepL and are not affected by an access outage. What can happen during a partial incident is that translation succeeds while glossary application does not, producing output that is correct but ignores your agreed terminology. If wording consistency matters for the text, it is worth re-running the translation after the incident clears.

How we measure this

We request DeepL's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means 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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required