Migrating off command-r — retirement date and replacement
Source check date not recorded.
Cohere is retiring command-r on 2025-09-15. The provider’s documented replacement is command-r-08-2024. This page is built from Cohere’s official deprecation notice and is rechecked weekly; the source link is below.
Past scheduled retirement. The published shutdown date has passed; this is a historical notice, not a live availability check.
When is command-r being deprecated?
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| command-r | Cohere | 2025-09-15 | command-r-08-2024 |
Source: Cohere deprecation notice · announced 2025-09-15
Test before switching
- Check the replacement's supported API endpoints and request parameters.
- Test your prompts, structured output, streaming and tool calls on staging.
- Compare quality, latency, pricing and rate limits on your workload.
- Keep a rollback path while the old model remains available.
Download retirement dates for your models.
What should I migrate command-r to?
Cohere documents command-r-08-2024 as the successor. This is not a compatibility guarantee: request parameters, API endpoints, pricing, tool calls and output behaviour may differ. Check the linked provider documentation and run your own workload before switching.
Measured latency of the Cohere API host
| Region | p50 TTFB | p95 | Uptime | Probes |
|---|---|---|---|---|
| Asia (Tokyo) | 175 ms | 221 ms | 100% | 288 |
| Europe (Germany) | 200 ms | 394 ms | 100% | 291 |
| South America (São Paulo) | 164 ms | 200 ms | 100% | 288 |
| US (Central) | 65 ms | 119 ms | 100% | 288 |
Edge latency to the provider’s API host over the last 24 hours, measured from 4 regions. This measures the endpoint, not the model: swapping models on the same host is not an inference benchmark or a promise about the replacement model. Compare edge latency →
What else retires on 2025-09-15?
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| command-r-plus | Cohere | 2025-09-15 | command-r-plus-08-2024 |
| command-light | Cohere | 2025-09-15 | command-r-08-2024 |
| command | Cohere | 2025-09-15 | command-r-08-2024 |
| command-r-03-2024 | Cohere | 2025-09-15 | command-r-08-2024 |
| command-r-plus-04-2024 | Cohere | 2025-09-15 | command-r-plus-08-2024 |
| summarize | Cohere | 2025-09-15 | — not named |
Same shutdown date. If you call more than one of these, they are one migration, not several.
Other Cohere models being retired
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| rerank-english-v2.0 | Cohere | 2025-04-30 | rerank-v3.5 |
| rerank-multilingual-v2.0 | Cohere | 2025-04-30 | rerank-v3.5 |
| embed-english-v2.0 | Cohere | 2026-04-04 | embed-english-v3.0 |
| embed-english-light-v2.0 | Cohere | 2026-04-04 | embed-english-v3.0 |
| embed-multilingual-v2.0 | Cohere | 2026-04-04 | embed-multilingual-v3.0 |
| c4ai-aya-expanse-8b | Cohere | 2026-04-04 | command-r7b-12-2024 |
| c4ai-aya-vision-8b | Cohere | 2026-04-04 | command-r7b-12-2024 |
How is this calendar maintained?
Entries are pulled from provider documentation by an automated weekly job and every one carries a link to its source. Nothing is inferred from blog posts or social media. When a provider changes a date, the change appears here after the next run and is visible in the changelog. The full calendar across all providers is on the deprecations page, and this provider’s own list is at Cohere deprecations.