From dd9e6aa2793412634586f714731d2de2f30b800f Mon Sep 17 00:00:00 2001 From: Jason Gardella Date: Tue, 2 Jun 2026 12:10:59 -0400 Subject: [PATCH 1/5] feat: add API Status Page links and release note --- docs/best-practices/error-handling.mdx | 2 +- docs/getting-started/quickstart.mdx | 7 +++++-- docs/resources/roadmap-and-release-notes.mdx | 6 ++++++ 3 files changed, 12 insertions(+), 3 deletions(-) diff --git a/docs/best-practices/error-handling.mdx b/docs/best-practices/error-handling.mdx index 86e40192..cb9ee7f6 100644 --- a/docs/best-practices/error-handling.mdx +++ b/docs/best-practices/error-handling.mdx @@ -10,7 +10,7 @@ Errors are indicated by [standard HTTP status codes](https://developer.mozilla.o * **HTTP 456: quota exceeded** **If you're a Free API user**, you'll receive this error when the monthly 500,000 character limit of your subscription has been reached. You can consider [upgrading your subscription](https://www.deepl.com/pro) if you need more character volume. **If you're a Pro API user**, you'll receive this error when your [Cost Control](/docs/best-practices/cost-control) limit has been reached, and you can increase or remove your Cost Control limit if you need to continue translating. You can also use the [usage endpoint](/api-reference/usage-and-quota) to find out your currently used and available quota. -* **HTTP 500: internal server error** This is an error you'll receive if there are temporary errors in DeepL Services. Your application should be configured to resend the requests after some delay. Specifically, we recommend implementing retries with exponential backoff. This is implemented in all of the official, DeepL-supported [client libraries](/docs/getting-started/client-libraries). +* **HTTP 500: internal server error** This is an error you'll receive if there are temporary errors in DeepL Services. Your application should be configured to resend the requests after some delay. Specifically, we recommend implementing retries with exponential backoff. This is implemented in all of the official, DeepL-supported [client libraries](/docs/getting-started/client-libraries). You can check the [API Status Page](https://api-status.deepl.com) for current service availability and incident information. The service dynamically adjusts to the load on the system. Please wait to stop receiving errors to send more requests again. As the service adapts, you will be able to send increasingly more requests within a given amount of time without encountering errors. diff --git a/docs/getting-started/quickstart.mdx b/docs/getting-started/quickstart.mdx index 20495e22..3001d5b0 100644 --- a/docs/getting-started/quickstart.mdx +++ b/docs/getting-started/quickstart.mdx @@ -256,8 +256,11 @@ New user? Follow these quick steps to get started with the DeepL API. DeepL Bridges - Developer Community - - Status Page + + API Status Page + + + DeepL Status Page (all services) Release Notes diff --git a/docs/resources/roadmap-and-release-notes.mdx b/docs/resources/roadmap-and-release-notes.mdx index f7530646..90a2ee85 100644 --- a/docs/resources/roadmap-and-release-notes.mdx +++ b/docs/resources/roadmap-and-release-notes.mdx @@ -15,6 +15,12 @@ rss: true - DeepL's developer documentation now exposes an MCP server at `https://developers.deepl.com/mcp`. - This enables AI tools to search the docs directly and get source-grounded answers about the DeepL API, with no API key required. - See the [Docs MCP Server](/docs/getting-started/docs-mcp-server) page for setup instructions. + +## June 1 - API Status Page +- Launched the [DeepL API Status Page](https://api-status.deepl.com), a dedicated dashboard for monitoring the operational status and availability of the DeepL API. +- View real-time status and 90-day availability for all API services across all supported regions. +- Supports both Pro and Free API tiers. +- Available in 19 languages. From 344d6d45d464728d406045c7e95c810def303d1a Mon Sep 17 00:00:00 2001 From: Jason Gardella Date: Wed, 3 Jun 2026 08:31:50 -0400 Subject: [PATCH 2/5] feat: add API Status Page to sidebar, footer, and as dedicated page --- docs.json | 12 +++++++++- docs/resources/api-status-page.mdx | 37 ++++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+), 1 deletion(-) create mode 100644 docs/resources/api-status-page.mdx diff --git a/docs.json b/docs.json index 4a52a6a2..d840dc9b 100644 --- a/docs.json +++ b/docs.json @@ -126,7 +126,8 @@ "docs/getting-started/docs-mcp-server", "docs/getting-started/test-your-api-requests-with-postman", "docs/resources/deepl-developer-community", - "docs/resources/open-api-spec" + "docs/resources/open-api-spec", + "docs/resources/api-status-page" ] }, { @@ -339,6 +340,15 @@ } }, "footer": { + "links": [ + { + "title": "Resources", + "links": [ + { "label": "API Status", "href": "https://api-status.deepl.com" }, + { "label": "DeepL Status (all services)", "href": "https://www.deeplstatus.com" } + ] + } + ], "socials": { "facebook": "https://www.facebook.com/DeepLcom/", "linkedin": "https://www.linkedin.com/company/deepl", diff --git a/docs/resources/api-status-page.mdx b/docs/resources/api-status-page.mdx new file mode 100644 index 00000000..6d1f15bf --- /dev/null +++ b/docs/resources/api-status-page.mdx @@ -0,0 +1,37 @@ +--- +title: "API Status Page" +description: "Monitor the operational status and availability of the DeepL API" +--- + +The [DeepL API Status Page](https://api-status.deepl.com) provides real-time information about the operational status of the DeepL API. + +## What you can check + +- **Current status** of all API services across Europe, Americas, and Asia-Pacific regions +- **90-day availability** history per service group (Translation, Write, Document Translation, Glossaries, and more) +- **Active and past incidents** affecting the API +- **Pro and Free API tier** status separately + +## When to check + +- If you're receiving HTTP 5xx errors from the API +- If you're experiencing elevated latency or timeouts +- Before investigating issues in your own integration — confirm the API is operational first + +## Regions + +The DeepL API operates in three regions. Each region has its own endpoint and status: + +| Region | API Endpoint | +|--------|-------------| +| Europe | `api.deepl.com` | +| Americas | `api-us.deepl.com` | +| Asia-Pacific | `api-jp.deepl.com` | + + + Go to the API Status Page + + + + For the status of all DeepL services (including web, desktop apps, and non-API products), see [deeplstatus.com](https://www.deeplstatus.com). + From 30e6292fbf0a78478b392fca2156bdcd07439531 Mon Sep 17 00:00:00 2001 From: Jason Gardella Date: Wed, 3 Jun 2026 08:32:35 -0400 Subject: [PATCH 3/5] fix: use 'all supported regions' instead of listing specific regions --- docs/resources/api-status-page.mdx | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/docs/resources/api-status-page.mdx b/docs/resources/api-status-page.mdx index 6d1f15bf..bfe41bcb 100644 --- a/docs/resources/api-status-page.mdx +++ b/docs/resources/api-status-page.mdx @@ -7,7 +7,7 @@ The [DeepL API Status Page](https://api-status.deepl.com) provides real-time inf ## What you can check -- **Current status** of all API services across Europe, Americas, and Asia-Pacific regions +- **Current status** of all API services across all supported regions - **90-day availability** history per service group (Translation, Write, Document Translation, Glossaries, and more) - **Active and past incidents** affecting the API - **Pro and Free API tier** status separately @@ -18,16 +18,6 @@ The [DeepL API Status Page](https://api-status.deepl.com) provides real-time inf - If you're experiencing elevated latency or timeouts - Before investigating issues in your own integration — confirm the API is operational first -## Regions - -The DeepL API operates in three regions. Each region has its own endpoint and status: - -| Region | API Endpoint | -|--------|-------------| -| Europe | `api.deepl.com` | -| Americas | `api-us.deepl.com` | -| Asia-Pacific | `api-jp.deepl.com` | - Go to the API Status Page From 32498d1bcbf05fe7fc4bf08095f886471c505506 Mon Sep 17 00:00:00 2001 From: Jason Gardella Date: Wed, 3 Jun 2026 08:34:58 -0400 Subject: [PATCH 4/5] fix: use 'items' instead of 'links' in footer schema --- docs.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs.json b/docs.json index d840dc9b..80314bca 100644 --- a/docs.json +++ b/docs.json @@ -343,7 +343,7 @@ "links": [ { "title": "Resources", - "links": [ + "items": [ { "label": "API Status", "href": "https://api-status.deepl.com" }, { "label": "DeepL Status (all services)", "href": "https://www.deeplstatus.com" } ] From 5f59fda45a6a4cfa6fa54c989b9e402988f4f08f Mon Sep 17 00:00:00 2001 From: Jason Gardella Date: Wed, 3 Jun 2026 11:14:58 -0400 Subject: [PATCH 5/5] fix: shorten footer link label to prevent truncation --- docs.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs.json b/docs.json index 80314bca..c6dc8cd0 100644 --- a/docs.json +++ b/docs.json @@ -345,7 +345,7 @@ "title": "Resources", "items": [ { "label": "API Status", "href": "https://api-status.deepl.com" }, - { "label": "DeepL Status (all services)", "href": "https://www.deeplstatus.com" } + { "label": "DeepL Status", "href": "https://www.deeplstatus.com" } ] } ],