Skip to content

Outage tracker / Cohere

Is Cohere down?

I'm having a problem

Operationalchecked moments ago

We reached Cohere from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Cohere (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:07 AM UTC
US-East745 msOperational
US-West341 msOperational
Europe451 msOperational
Asia-Pacific507 msOperational
US-Central352 msOperational
Canada129 msOperational
UK330 msOperational
Southeast Asia1255 msOperational
Australia624 msOperational
South America887 msOperational
their status pagetheir claim, not our reading

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

from Cohere's own status page, checked Sep 5, 2026, 1:46 AM UTC
Our probes and Cohere's own status page agree: both show Cohere as reachable right now.

Cohere's own component breakdown, as they publish it

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

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
889msp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.0s2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.3s2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.5s2026-08-29 UTC: p95 1.9s2026-08-30 UTC: p95 2.2s2026-08-31 UTC: p95 1.8s2026-09-01 UTC: p95 1.8s2026-09-02 UTC: p95 1.9s2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.6s2026-09-05 UTC: p95 889ms
Aug 7Aug 21Sep 5
US-West
477msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 576ms2026-08-23 UTC: p95 591ms2026-08-24 UTC: p95 650ms2026-08-25 UTC: p95 677ms2026-08-26 UTC: p95 648ms2026-08-27 UTC: p95 701ms2026-08-28 UTC: p95 758ms2026-08-29 UTC: p95 532ms2026-08-30 UTC: p95 781ms2026-08-31 UTC: p95 631ms2026-09-01 UTC: p95 530ms2026-09-02 UTC: p95 611ms2026-09-03 UTC: p95 603ms2026-09-04 UTC: p95 527ms2026-09-05 UTC: p95 477ms
Aug 7Aug 21Sep 5
Europe
670msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 535ms2026-08-23 UTC: p95 674ms2026-08-24 UTC: p95 614ms2026-08-25 UTC: p95 628ms2026-08-26 UTC: p95 797ms2026-08-27 UTC: p95 682ms2026-08-28 UTC: p95 828ms2026-08-29 UTC: p95 712ms2026-08-30 UTC: p95 611ms2026-08-31 UTC: p95 699ms2026-09-01 UTC: p95 880ms2026-09-02 UTC: p95 767ms2026-09-03 UTC: p95 718ms2026-09-04 UTC: p95 773ms2026-09-05 UTC: p95 670ms
Aug 7Aug 21Sep 5
Asia-Pacific
681msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 746ms2026-08-23 UTC: p95 831ms2026-08-24 UTC: p95 1.2s2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 947ms2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 982ms2026-08-29 UTC: p95 978ms2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.3s2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 952ms2026-09-05 UTC: p95 681ms
Aug 7Aug 21Sep 5
US-Central
626msp95 · 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-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 626ms
Aug 7Aug 21Sep 5
Canada
532msp95 · 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-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 532ms
Aug 7Aug 21Sep 5
UK
351msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 416ms2026-09-04 UTC: p95 561ms2026-09-05 UTC: p95 351ms
Aug 7Aug 21Sep 5
Southeast Asia
1.3sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
Australia
1.0sp95 · 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-03 UTC: p95 1.3s2026-09-04 UTC: p95 881ms2026-09-05 UTC: p95 1.0s
Aug 7Aug 21Sep 5
South America
1.6sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.6s
Aug 7Aug 21Sep 5

Is it Cohere, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 745msstatus code: 401checked: Sep 5, 2026, 2:07 AM 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
      Operationallatency: 341msstatus code: 401checked: Sep 5, 2026, 2:07 AM 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
      Operationallatency: 352msstatus code: 401checked: Sep 5, 2026, 2:02 AM 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
      Operationallatency: 129msstatus code: 401checked: Sep 5, 2026, 1:52 AM 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
    Operationallatency: 887msstatus code: 401checked: Sep 5, 2026, 2:00 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Cohere normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 451msstatus code: 401checked: Sep 5, 2026, 1:58 AM 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
      Operationallatency: 330msstatus code: 401checked: Sep 5, 2026, 1:58 AM 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 507msstatus code: 401checked: Sep 5, 2026, 2:02 AM 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
      Operationallatency: 1255msstatus code: 401checked: Sep 5, 2026, 1:50 AM 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
      Operationallatency: 624msstatus code: 401checked: Sep 5, 2026, 1:59 AM 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 outages

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

measured 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 measurements and Cohere's own claim at the time, side by side.

Full availability history for Cohere: 90-day availability by region, month-by-month uptime, and every incident 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

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Cohere, and again when they can reach it again. That is our own measurement from ten regions, not Cohere's status page. No account, no card.

Delivery channel

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

Put this badge in your README

Cohere uptime measured by RealUptimeLive, from this page's own readings.
[![Cohere uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Cohere's SLA implies, from our measurement

At or above your target

We measured none of downtime for Cohere over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Cohere's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

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
RealUptime is not affiliated with Cohere; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.