Where does this status come from?

From Cohere's own status page API at https://status.cohere.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Cohere's words.

How can my agent or app check Cohere status?

Fetch https://upbutler.com/status/cohere/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"cohere"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Cohere's?

Add "cohere" to the dependencies of your UpButler workspace. When one of your monitors fails while Cohere has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Cohere down?

Right now

No. Cohere is operational.

No incidents reported.

Read from status.cohere.com 3 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/cohere/status.agent.json

MCP: upstream_status {"service":"cohere"}

Command models, embeddings and rerank. A rerank outage degrades search quality quietly instead of failing loudly.

What Cohere reports

Operational

Taken as is from Cohere's own status page API. Incident titles and component names below are theirs.

Open status.cohere.com

UpButler's independent probe

There is no keyless endpoint of Cohere that says anything useful, so UpButler does not probe it. To check your own Cohere account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Cohere components

25 operational

All EndpointsOperational
embeddingsOperational
All ModelsOperational
command-a-plus-05-2026Operational
command-a-reasoning-08-2025Operational
command-a-vision-07-2025Operational
command-a-translate-08-2025Operational
command-a-03-2025Operational
command-r-plus-08-2024Operational
command-r-08-2024Operational
command-r7b-12-2024Operational
embed-v4.0Operational
embed-english-v3.0Operational
embed-english-light-v3.0Operational
embed-multilingual-v3.0Operational
embed-multilingual-light-v3.0Operational
rerank-v4.0-fastOperational
rerank-v4.0-proOperational
rerank-v3.5Operational
rerank-english-v3.0Operational
rerank-multilingual-v3.0Operational
c4ai-aya-vision-32bOperational
c4ai-aya-expanse-32bOperational
tiny-aya-baseOperational
tiny-aya-globalOperational

Cohere incidents, last 90 days

No finished incidents on record yet. UpButler keeps what Cohere publishes for 90 days from the day it starts tracking a service.

Tell your outage from Cohere's

Declare that your project depends on Cohere. When one of your monitors fails while Cohere has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - cohere

Ask before you retry

curl -s https://upbutler.com/status/cohere/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "cohere",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Cohere down right now?: No. As of 2026-10-10 05:09 UTC, Cohere is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Cohere's own status page API at https://status.cohere.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Cohere's words.
How can my agent or app check Cohere status?: Fetch https://upbutler.com/status/cohere/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"cohere"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Cohere's?: Add "cohere" to the dependencies of your UpButler workspace. When one of your monitors fails while Cohere has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in ai models and tooling

UpButler is not affiliated with Cohere. Status and incident text belong to Cohere and are read from their public status source; the probe result is UpButler's own measurement.