Try Bifrost Enterprise free for 14 days.
Request access
Cohere
[ LIVE STATUS ]

Is Cohere Down?

Command R+, Command R, Embed, Rerank, Coral, and Cohere API services.

Official status data last reflected here:

All Systems Operational
Live · updated just now

[ STATUS AT A GLANCE ]

Operational
Current Status
All Systems Operational
24
Components
Service areas tracked on this page
4
90d Incidents
Incidents reported in the last 90 days

System Components

Current status of individual Cohere services

DocsAll Systems Operational
system-wide incident history
90 days agoToday
WebsiteAll Systems Operational
system-wide incident history
90 days agoToday
embeddingsAll Systems Operational
system-wide incident history
90 days agoToday
embed-v4.0All Systems Operational
system-wide incident history
90 days agoToday
command-a-reasoning-08-2025All Systems Operational
system-wide incident history
90 days agoToday
command-a-03-2025All Systems Operational
system-wide incident history
90 days agoToday
embed-multilingual-light-v3.0All Systems Operational
system-wide incident history
90 days agoToday
CoralAll Systems Operational
system-wide incident history
90 days agoToday
embed-english-v3.0All Systems Operational
system-wide incident history
90 days agoToday
InfrastructureAll Systems Operational
system-wide incident history
90 days agoToday
PlaygroundAll Systems Operational
system-wide incident history
90 days agoToday
embed-english-light-v3.0All Systems Operational
system-wide incident history
90 days agoToday
rerank-english-v3.0All Systems Operational
system-wide incident history
90 days agoToday
command-r-082024All Systems Operational
system-wide incident history
90 days agoToday
command-a-vision-07-2025All Systems Operational
system-wide incident history
90 days agoToday
command-r7bAll Systems Operational
system-wide incident history
90 days agoToday
rerank-multilingual-v3.0All Systems Operational
system-wide incident history
90 days agoToday
rerank-v4.0-fastAll Systems Operational
system-wide incident history
90 days agoToday
rerank-english-v2.0All Systems Operational
system-wide incident history
90 days agoToday
rerank-v3.5All Systems Operational
system-wide incident history
90 days agoToday
rerank-v4.0-proAll Systems Operational
system-wide incident history
90 days agoToday
command-r-plus-082024All Systems Operational
system-wide incident history
90 days agoToday
rerank-multilingual-v2.0All Systems Operational
system-wide incident history
90 days agoToday
embed-multilingual-v3.0All Systems Operational
system-wide incident history
90 days agoToday
[ AUTOMATIC FAILOVER ]

Cohere down? Route around it.

When Cohere has issues, Bifrost automatically routes your requests to a healthy alternative provider. Zero code changes. 99.999% effective uptime.

About Cohere

What Cohere does, where the data on this page comes from, and recent reliability

[ ABOUT COHERE ]

About Cohere

Cohere provides Command models, Embed, Rerank, and Coral. Cohere status is especially important for production retrieval and ranking systems where latency and model availability directly shape search relevance and workflow quality.

This page pulls data from Cohere's official status page to show current service health, any active incidents, and a history of recent issues, all in one view.

Command modelsEmbedRerankCoral

[ DATA SOURCES ]

Full incident history available

Cohere publishes detailed component status, a full incident archive, and scheduled maintenance data through their official status page.

  • Data pulled from Cohere's official status page (status.cohere.com)
  • Refreshed every 60 seconds
  • Covers Command models, Embed, Rerank, and Coral
  • Includes full incident archive and scheduled maintenance history

[ RELIABILITY ]

Recent reliability

  • 4 incidents reported over the last 90 days.
  • Last reported incident was 17 days ago.
  • All 24 monitored components are currently operational.

[ COMMON USE CASES ]

How teams use Cohere

Cohere status is especially important for production retrieval and ranking systems where latency and model availability directly shape search relevance and workflow quality.

Enterprise search
Retrieval pipelines
Classification and reranking

Incidents & Maintenance

Active incidents, scheduled maintenance, and incident history for Cohere

Past Incidents

Docs Platform Degraded Performance

Apr 20, 2026 · Resolved Apr 20, 2026

Resolvedcritical
ResolvedApr 20, 2026, 10:28 PM UTC

InvestigatingApr 20, 2026, 10:16 PM UTC

Multiple Model Disruptions

Apr 13, 2026 · Resolved Apr 13, 2026

Resolvedminor
ResolvedApr 13, 2026, 9:00 PM UTC

MonitoringApr 13, 2026, 7:45 PM UTC

InvestigatingApr 13, 2026, 7:36 PM UTC

Scheduled DB Maintenance: Model authentication and API access momentarily affected

Apr 11, 2026 · Resolved Apr 11, 2026

Resolvedminor
ResolvedApr 11, 2026, 3:39 PM UTC

IdentifiedApr 11, 2026, 3:31 PM UTC

Some chat models are unresponsive or timing out

Feb 13, 2026 · Resolved Feb 13, 2026

Resolvedmajor
ResolvedFeb 13, 2026, 5:51 AM UTC

MonitoringFeb 13, 2026, 5:35 AM UTC

InvestigatingFeb 13, 2026, 4:34 AM UTC

Chat models return 503 service error when /v1/chat requests omit message and chat_history while providing tool_results

Oct 18, 2025 · Resolved Oct 18, 2025

Resolvednone
ResolvedOct 18, 2025, 10:23 PM UTC

IdentifiedOct 18, 2025, 9:46 PM UTC

logprobs param degeraded for `command-a-03-2025` and `command-a-reasoning-08-2025`

Oct 1, 2025 · Resolved Oct 1, 2025

Resolvedminor
ResolvedOct 1, 2025, 7:46 PM UTC

InvestigatingOct 1, 2025, 3:56 PM UTC

Command-a-vision-07-2025 degraded performance

Aug 7, 2025 · Resolved Aug 7, 2025

Resolvedminor
ResolvedAug 7, 2025, 8:56 PM UTC

IdentifiedAug 7, 2025, 8:46 PM UTC

Model serving infrastructure outage

Jul 25, 2025 · Resolved Jul 25, 2025

Resolvedcritical
ResolvedJul 25, 2025, 7:52 PM UTC

MonitoringJul 25, 2025, 7:12 PM UTC

IdentifiedJul 25, 2025, 6:25 PM UTC

InvestigatingJul 25, 2025, 4:33 PM UTC

InvestigatingJul 25, 2025, 3:54 PM UTC

GCP Outage

Jun 12, 2025 · Resolved Jun 12, 2025

Resolvedminor
ResolvedJun 12, 2025, 10:44 PM UTC

MonitoringJun 12, 2025, 7:02 PM UTC

Degraded service affecting embed-v4.0

May 21, 2025 · Resolved May 21, 2025

Resolvedminor
ResolvedMay 21, 2025, 7:15 PM UTC

InvestigatingMay 21, 2025, 4:53 PM UTC

Degraded service affecting embedding models

May 8, 2025 · Resolved May 13, 2025

Resolvedminor
ResolvedMay 13, 2025, 3:01 PM UTC

MonitoringMay 8, 2025, 5:14 PM UTC

InvestigatingMay 8, 2025, 2:25 PM UTC

Degraded Performance - Increased Latency - Command-a-03-2025/command-r-plus-08-2024

Apr 3, 2025 · Resolved Apr 4, 2025

Resolvedminor
ResolvedApr 4, 2025, 8:58 PM UTC

ResolvedApr 4, 2025, 8:58 PM UTC

MonitoringApr 3, 2025, 9:11 PM UTC

IdentifiedApr 3, 2025, 5:34 PM UTC

InvestigatingApr 3, 2025, 5:29 PM UTC

Degraded Performance: command-a-03-2025 - Increased Latency

Apr 2, 2025 · Resolved Apr 3, 2025

Resolvedminor
ResolvedApr 3, 2025, 1:49 AM UTC

MonitoringApr 2, 2025, 10:20 PM UTC

High latency

Mar 29, 2025 · Resolved Mar 29, 2025

Resolvedminor
ResolvedMar 29, 2025, 7:14 PM UTC

InvestigatingMar 29, 2025, 7:03 PM UTC

Increased Latency

Mar 28, 2025 · Resolved Mar 28, 2025

Resolvedminor
ResolvedMar 28, 2025, 11:58 PM UTC

InvestigatingMar 28, 2025, 8:40 PM UTC

Increased Latency

Mar 28, 2025 · Resolved Mar 28, 2025

Resolvedminor
ResolvedMar 28, 2025, 7:38 PM UTC

InvestigatingMar 28, 2025, 7:17 PM UTC

Elevated Latency

Mar 27, 2025 · Resolved Mar 27, 2025

Resolvedminor
ResolvedMar 27, 2025, 6:02 PM UTC

InvestigatingMar 27, 2025, 5:51 PM UTC

CommandR / CommandR plus: Elevated Error Rate

Mar 24, 2025 · Resolved Mar 24, 2025

Resolvedminor
ResolvedMar 24, 2025, 8:26 PM UTC

MonitoringMar 24, 2025, 6:33 PM UTC

Rerank Endpoint: Degraded Service

Mar 20, 2025 · Resolved Mar 20, 2025

Resolvedminor
ResolvedMar 20, 2025, 7:29 PM UTC

InvestigatingMar 20, 2025, 6:00 PM UTC

Chat Endpoint: Encountering Increased Error rate

Mar 19, 2025 · Resolved Mar 19, 2025

Resolvedminor
ResolvedMar 19, 2025, 11:46 AM UTC

MonitoringMar 19, 2025, 1:35 AM UTC

InvestigatingMar 19, 2025, 1:12 AM UTC

Frequently Asked Questions

Is Cohere down right now?

Check the status indicator at the top of this page. It pulls directly from Cohere's official status page. If Cohere is experiencing any issues, you'll see it reflected here. This real-time monitoring helps teams quickly identify whether performance problems are caused by Cohere infrastructure or their own systems.

What does this Cohere status page track?

This page tracks Command models, Embed, Rerank, and Coral using data from Cohere's official status page. You can see current component health, active incidents, and a history of past issues. This visibility is crucial for teams building resilient AI applications that need to route around provider outages.

How often is Cohere status updated here?

We check Cohere's status page every 60 seconds to ensure you get near real-time status updates. How quickly issues show up here depends on how fast Cohere updates their own official status. For production systems that need instant failover, Bifrost can automatically detect and route around degraded providers.

Why monitor Cohere status?

Cohere status is especially important for production retrieval and ranking systems where latency and model availability directly shape search relevance and workflow quality. Real-time status monitoring enables proactive incident response and helps teams decide when to route traffic to alternative providers for maximum uptime.

What should I do when Cohere goes down?

When Cohere experiences an outage, the best practice is automatic failover to alternative AI providers. Bifrost is an open-source AI gateway that automatically detects Cohere degradation and routes LLM traffic to healthy alternatives like OpenAI, Anthropic, Azure OpenAI, keeping your application running with zero manual intervention. This intelligent routing ensures your users never experience downtime from a single provider's issues.

How can I prevent Cohere downtime from affecting my application?

Production AI applications should never depend on a single provider. Bifrost AI Gateway provides automatic multi-provider failover, intelligent load balancing, and health-based routing. When Cohere degrades, Bifrost instantly routes requests to operational alternatives while maintaining API compatibility. This architecture approach is used by teams running mission-critical AI features.

What are common causes of Cohere outages and degraded performance?

Common causes of Cohere issues include infrastructure scaling challenges, regional cloud provider problems, API gateway overload, and deployment errors. Monitor this page to stay informed, and consider implementing automatic failover with Bifrost to maintain uptime during Cohere incidents.

Alternative Providers for Automatic Failover

When Cohere experiences issues, Bifrost AI Gateway can automatically route your LLM traffic to these alternatives

💡 Build resilient AI apps: Configure Bifrost to automatically detect Cohere outages and route requests to healthy alternatives. This multi-provider approach ensures your application maintains uptime even when individual providers experience issues. Learn more about Bifrost AI Gateway