Skip to content

Outage tracker / Cohere

Is Cohere down?

I'm having a problem

Vendor reports no incidentWhat Cohere reports

Cohere reports no incident on its status page.

As of the last successful poll, 2026-10-23 21:43 UTC.

Cohere's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Awaiting datachecked moments ago

Our checks of Cohere pass from 9 of the 10 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

As of Oct 23, 2026, 9:45 PM UTC, RealUptime's checks of Cohere passed in all 9 regions that returned a reading. RealUptime could not obtain a reading from South America, which is a fact about our own check there and is not evidence about Cohere.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 9:45 PM UTC
US-East1422 msChecks passing
US-West1044 msChecks passing
Europe499 msChecks passing
Asia-Pacific1014 msChecks passing
US-Central197 msChecks passing
Canada882 msChecks passing
UK493 msChecks passing
Southeast Asia2400 msChecks passing
Australia448 msChecks passing
South America11928 msAwaiting data
their status pagetheir claim, not our reading

Cohere reports: All systems operational (“All Systems Operational”)

from Cohere's own status page, checked Oct 23, 2026, 9:27 PM UTC

Cohere's own component breakdown, as they publish it

  • 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

These are Cohere's components, named and scored by Cohere. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Cohere's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Cohere response time, by region

US-East
1.5sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 547ms2026-09-25 UTC: p95 807ms2026-09-26 UTC: p95 795ms2026-09-27 UTC: p95 717ms2026-09-28 UTC: p95 769ms2026-09-29 UTC: p95 802ms2026-09-30 UTC: p95 741ms2026-10-01 UTC: p95 901ms2026-10-02 UTC: p95 633ms2026-10-03 UTC: p95 970ms2026-10-04 UTC: p95 977ms2026-10-05 UTC: p95 910ms2026-10-06 UTC: p95 927ms2026-10-07 UTC: p95 883ms2026-10-08 UTC: p95 913ms2026-10-09 UTC: p95 999ms2026-10-10 UTC: p95 957ms2026-10-11 UTC: p95 964ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 866ms2026-10-14 UTC: p95 826ms2026-10-15 UTC: p95 797ms2026-10-16 UTC: p95 851ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.5s
Sep 24Oct 8Oct 23
US-West
2.0sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 606ms2026-09-25 UTC: p95 710ms2026-09-26 UTC: p95 654ms2026-09-27 UTC: p95 596ms2026-09-28 UTC: p95 606ms2026-09-29 UTC: p95 516ms2026-09-30 UTC: p95 555ms2026-10-01 UTC: p95 634ms2026-10-02 UTC: p95 575ms2026-10-03 UTC: p95 623ms2026-10-04 UTC: p95 855ms2026-10-05 UTC: p95 860ms2026-10-06 UTC: p95 782ms2026-10-07 UTC: p95 827ms2026-10-08 UTC: p95 772ms2026-10-09 UTC: p95 826ms2026-10-10 UTC: p95 840ms2026-10-11 UTC: p95 775ms2026-10-12 UTC: p95 825ms2026-10-13 UTC: p95 940ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 2.0s
Sep 24Oct 8Oct 23
Europe
916msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 802ms2026-09-25 UTC: p95 947ms2026-09-26 UTC: p95 979ms2026-09-27 UTC: p95 939ms2026-09-28 UTC: p95 889ms2026-09-29 UTC: p95 640ms2026-09-30 UTC: p95 592ms2026-10-01 UTC: p95 700ms2026-10-02 UTC: p95 729ms2026-10-03 UTC: p95 757ms2026-10-04 UTC: p95 700ms2026-10-05 UTC: p95 672ms2026-10-06 UTC: p95 762ms2026-10-07 UTC: p95 800ms2026-10-08 UTC: p95 916ms2026-10-09 UTC: p95 874ms2026-10-10 UTC: p95 915ms2026-10-11 UTC: p95 929ms2026-10-12 UTC: p95 916ms2026-10-13 UTC: p95 769ms2026-10-14 UTC: p95 843ms2026-10-15 UTC: p95 733ms2026-10-16 UTC: p95 800ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 832ms2026-10-23 UTC: p95 916ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.8sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 952ms2026-09-25 UTC: p95 753ms2026-09-26 UTC: p95 842ms2026-09-27 UTC: p95 719ms2026-09-28 UTC: p95 730ms2026-09-29 UTC: p95 902ms2026-09-30 UTC: p95 865ms2026-10-01 UTC: p95 875ms2026-10-02 UTC: p95 985ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 912ms2026-10-05 UTC: p95 903ms2026-10-06 UTC: p95 845ms2026-10-07 UTC: p95 783ms2026-10-08 UTC: p95 877ms2026-10-09 UTC: p95 868ms2026-10-10 UTC: p95 918ms2026-10-11 UTC: p95 776ms2026-10-12 UTC: p95 896ms2026-10-13 UTC: p95 853ms2026-10-14 UTC: p95 973ms2026-10-15 UTC: p95 851ms2026-10-16 UTC: p95 909ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.8s
Sep 24Oct 8Oct 23
US-Central
667msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 762ms2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 814ms2026-09-30 UTC: p95 804ms2026-10-01 UTC: p95 805ms2026-10-02 UTC: p95 717ms2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 687ms2026-10-23 UTC: p95 667ms
Sep 24Oct 8Oct 23
Canada
1.5sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 749ms2026-09-25 UTC: p95 748ms2026-09-26 UTC: p95 749ms2026-09-27 UTC: p95 717ms2026-09-28 UTC: p95 722ms2026-09-29 UTC: p95 718ms2026-09-30 UTC: p95 606ms2026-10-01 UTC: p95 855ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 989ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 992ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.5s
Sep 24Oct 8Oct 23
UK
701msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 557ms2026-09-25 UTC: p95 524ms2026-09-26 UTC: p95 547ms2026-09-27 UTC: p95 491ms2026-09-28 UTC: p95 496ms2026-09-29 UTC: p95 444ms2026-09-30 UTC: p95 448ms2026-10-01 UTC: p95 842ms2026-10-02 UTC: p95 839ms2026-10-03 UTC: p95 847ms2026-10-04 UTC: p95 858ms2026-10-05 UTC: p95 797ms2026-10-06 UTC: p95 818ms2026-10-07 UTC: p95 706ms2026-10-08 UTC: p95 661ms2026-10-09 UTC: p95 697ms2026-10-10 UTC: p95 669ms2026-10-11 UTC: p95 698ms2026-10-12 UTC: p95 678ms2026-10-13 UTC: p95 664ms2026-10-14 UTC: p95 668ms2026-10-15 UTC: p95 669ms2026-10-16 UTC: p95 679ms2026-10-17 UTC: p95 944ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 851ms2026-10-23 UTC: p95 701ms
Sep 24Oct 8Oct 23
Southeast Asia
2.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.8s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.1s
Sep 24Oct 8Oct 23
Australia
649msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 977ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 865ms2026-10-01 UTC: p95 820ms2026-10-02 UTC: p95 706ms2026-10-03 UTC: p95 688ms2026-10-04 UTC: p95 725ms2026-10-05 UTC: p95 666ms2026-10-06 UTC: p95 666ms2026-10-07 UTC: p95 637ms2026-10-08 UTC: p95 659ms2026-10-09 UTC: p95 701ms2026-10-10 UTC: p95 726ms2026-10-11 UTC: p95 721ms2026-10-12 UTC: p95 724ms2026-10-13 UTC: p95 814ms2026-10-14 UTC: p95 841ms2026-10-15 UTC: p95 801ms2026-10-16 UTC: p95 745ms2026-10-17 UTC: p95 758ms2026-10-18 UTC: p95 812ms2026-10-19 UTC: p95 876ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 968ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 649ms
Sep 24Oct 8Oct 23
South America
5.7sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 943ms2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 5.7s
Sep 24Oct 8Oct 23
Why some readings show as awaiting data. 2 of 20 readings for Cohere came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Cohere's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on Cohere

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Cohere. It cannot diagnose Cohere's own systems.

What we measured, function by function

Cohere answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Awaiting data
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Awaiting data

Email me when Cohere reports an incident on its status page, and again when it reports it resolved.

Get an email when Cohere reports an incident

Email me when Cohere reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Cohere's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1422msstatus code: 401checked: Oct 23, 2026, 9:45 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Cohere normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1044msstatus code: 401checked: Oct 23, 2026, 9:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Cohere normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 197msstatus code: 401checked: Oct 23, 2026, 9:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Cohere normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 882msstatus code: 401checked: Oct 23, 2026, 9:39 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Cohere normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Awaiting datalatency: 11928msstatus code: nonecheck reading: nonechecked: Oct 23, 2026, 9:33 PM UTC
    0 people in the last 5 minutesNot enough reports to sayCohere refused our South America probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from South America to say anything on their own.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 499msstatus code: 401checked: Oct 23, 2026, 9:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Cohere normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 493msstatus code: 401checked: Oct 23, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Cohere normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1014msstatus code: 401checked: Oct 23, 2026, 9:45 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Cohere normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2400msstatus code: 401checked: Oct 23, 2026, 9:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Cohere normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 448msstatus code: 401checked: Oct 23, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Cohere normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Cohere, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Cohere yet, which is not evidence that nothing is wrong.

Recent probe events

Multiple Endpoint Disruptions, 4h 22mdeclared on their status page2026-09-01
Documentation Content Loading Issues, 57mdeclared on their status page2026-08-05
Dashboard Login Service Disruption, 51mdeclared on their status page2026-07-23
/audio/transcriptions endpoint returns error for audio files with unexpected sampling rate, 2h 54mdeclared on their status page2026-06-01
Docs Platform Degraded Performance, 13mdeclared on their status page2026-04-20
Multiple Model Disruptions, 1h 25mdeclared on their status page2026-04-13
Scheduled DB Maintenance: Model authentication and API access momentarily affected, 9mdeclared on their status page2026-04-11
Some chat models are unresponsive or timing out, 1h 18mdeclared on their status page2026-02-13

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Cohere since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Cohere covering any window you pick, with our check readings and Cohere's own claim at the time, side by side.

Full check history for Cohere: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Cohere uptime by RealUptime's checksLive, from this page's own readings.
[![Cohere uptime by RealUptime's checks](https://realuptime.io/outages/cohere/badge.svg?days=30)](https://realuptime.io/outages/cohere)
<a href="https://realuptime.io/outages/cohere"><img src="https://realuptime.io/outages/cohere/badge.svg?days=30" alt="Cohere uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Cohere down?", https://realuptime.io/outages/cohere. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.cohere.com/v1/models
secondary
https://cohere.com/
secondary
https://status.cohere.com/api/v2/status.json

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.cohere.com

RealUptime is not affiliated with Cohere; the name identifies what we checked, and nothing here speaks for Cohere's own team. We send a single web request to Cohere from 10 regions on our own schedule and time the response. We do not see inside Cohere's systems, do not use an account or real transaction, and are not the same signal Cohere's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Cohere is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.