feat: add API Status Page links and release note

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",
+        "items": [
+          { "label": "API Status", "href": "https://api-status.deepl.com" },
+          { "label": "DeepL Status", "href": "https://www.deeplstatus.com" }
+        ]
+      }
+    ],
     "socials": {
       "facebook": "https://www.facebook.com/DeepLcom/",
       "linkedin": "https://www.linkedin.com/company/deepl",

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.
 

docs/getting-started/quickstart.mdx

@@ -256,8 +256,11 @@ New user? Follow these quick steps to get started with the DeepL API.
   <Card icon="bridge" horizontal href="https://www.deepl-bridges.com/">
     DeepL Bridges - Developer Community
   </Card>
-  <Card icon="signal-stream" horizontal href="https://www.deeplstatus.com/">
-    Status Page
+  <Card icon="signal-stream" horizontal href="https://api-status.deepl.com/">
+    API Status Page
+  </Card>
+  <Card icon="tower-broadcast" horizontal href="https://www.deeplstatus.com/">
+    DeepL Status Page (all services)
   </Card>
   <Card icon="notes" horizontal href="/docs/resources/release-notes">
     Release Notes

docs/resources/api-status-page.mdx

@@ -0,0 +1,27 @@
+---
+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 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
+
+## 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
+
+<Card icon="signal-stream" href="https://api-status.deepl.com">
+  Go to the API Status Page
+</Card>
+
+<Note>
+  For the status of all DeepL services (including web, desktop apps, and non-API products), see [deeplstatus.com](https://www.deeplstatus.com).
+</Note>

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.
 </Update>
 
 <Update label="May 2026">