Skip to main content
Cohere logo

Is Cohere Down?

No — Cohere is up
Cohere's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 837 ms

Right now

The verdict is the worse of these two. How we decide

Cohere's status page

status.cohere.com · read · checked every 3 minutes

Operational
Cohere's components, as its status page reports them
ComponentStatus
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
13 more, all operational · show all 25
All of Cohere's components
ComponentStatus
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
Open their status page

FlareWarden checks

dashboard.cohere.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
837 ms
Checked

By region

  • Ashburn reachable, 471 ms
  • Chicago reachable, 496 ms
  • Frankfurt reachable, 620 ms
  • Johannesburg reachable, 1328 ms
  • London reachable, 823 ms
  • Los Angeles reachable, 702 ms
  • São Paulo reachable, 1050 ms
  • Tokyo reachable, 1206 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn22 ms1 ms7 ms460 ms
Chicago10 ms1 ms26 ms495 ms
Frankfurt15 ms2 ms8 ms619 ms
Johannesburg7 ms1 ms76 ms1328 ms
London12 ms2 ms7 ms820 ms
Los Angeles54 ms2 ms28 ms700 ms
São Paulo171 ms1 ms15 ms939 ms
Tokyo212 ms2 ms8 ms1203 ms
We check that dashboard.cohere.com loads, not every feature behind it. Test it yourself

History

Incidents Cohere reported

Since Oct 22, 15 days · from status.cohere.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Cohere website availability

Measured by FlareWarden · dashboard.cohere.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
1260ms

Last 30 days

71-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 32 checks
Oct 17: 100.00% uptime, 32 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 31 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of dashboard.cohere.com from multiple regions every 6 hours. Cohere's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Cohere does

Cohere builds large language models sold as an API for enterprises, covering text generation, embeddings, reranking and retrieval-augmented search. It targets companies that want models deployed in their own cloud or a private environment rather than only as a public API, and it sits underneath search, classification and assistant features built on top of it.

What an outage looks like

API calls return 5xx responses or take far longer than usual to complete, and features built on Cohere such as semantic search, reranking and chat assistants either fail or fall back to whatever your code does when a model call errors. The dashboard at dashboard.cohere.com may fail to load. Degraded latency across endpoints is a more common pattern here than a hard outage.

What to do about it

Check status.cohere.com, which separates Endpoints, Models, Infrastructure, Playground, Docs and Website and lists 25 models individually, so confirm whether the model you call is the affected one. Watch the name collision: status.cohere.io belongs to a different company. If reranking is the degraded piece, serving unranked results is usually better than serving none.

Is it down for everyone, or just you?

If this page says Cohere is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

O
OpenRouter
Groq
Groq
M
Mistral AI
Together AI
Together AI

Cohere outage FAQ

Which Cohere is this page about?
Cohere the AI company at cohere.com, which sells large language models to enterprises. Two other companies share the name: Cohere at cohere.io, a customer support cobrowsing product with its own status page at status.cohere.io, and Cohere Health at coherehealth.com. A search for cohere status returns all three, which is worth knowing before you read the wrong page.
Is the whole platform down or just one model?
Often just one model. Cohere's status page groups 25 models as individual components beneath a Models heading, kept separate from Endpoints and Infrastructure. A specific model degrading while the API itself is healthy is a different incident from the API being unreachable, and only the per-component view tells them apart.
What do Cohere incidents usually look like?
Slower rather than broken. Its status page carries a published incident titled Degraded performance across endpoints and models, which is the shape most Cohere incidents take. Degraded latency is harder to spot from inside an application than an outright error, because calls still succeed but take long enough to blow through user-facing timeouts.
What should my application do when Cohere is slow?
Set an explicit timeout on model calls and decide the fallback before you need it. Degraded latency is the common failure mode here, and without a timeout a slow Cohere call becomes a slow page for your own users. A cached result, a smaller model or a plain message all beat a request that hangs.

How we measure this

  • We request Cohere's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Cohere publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Cohere itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Cohere goes down

We check Cohere every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required