Skip to content

Outage tracker

Cohere: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, Cohere's declared record, and how the two compare.

← Back to Cohere's live status

We started measuring Cohere on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Cohere's own status page declared. Below it, any public chatter we saw about Cohere and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Cohere's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Cohere in the last 24 hours, which is not evidence that nothing is wrong.
Cohere's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Cohere's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Cohere next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%1843
US-West100.00%1830
Europe100.00%1759
Asia-Pacific99.94%1559
US-Central100.00%175
Canada100.00%175
UK100.00%174
Southeast Asia100.00%143
Australia100.00%141
South America100.00%165

Monthly summary

Tracking Cohere since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Cohere: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Cohere's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Cohere in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Cohere's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Cohere since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Cohere's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Multiple Endpoint DisruptionsMinor incident
Sep 1, 2026, 3:41 PM UTC to Sep 1, 2026, 8:03 PM UTC (4h 22m)resolved
their latest update (Sep 1, 2026, 8:03 PM UTC): 🎉 The issue has been resolved and we are back to normal.
Documentation Content Loading IssuesPartial outage
Aug 5, 2026, 7:36 PM UTC to Aug 5, 2026, 8:33 PM UTC (57 min)resolved
their latest update (Aug 5, 2026, 8:35 PM UTC): 🎉 The issue has been resolved and we are back to normal.
Dashboard Login Service DisruptionPartial outage
Jul 23, 2026, 10:56 PM UTC to Jul 23, 2026, 11:46 PM UTC (51 min)resolved
their latest update (Jul 23, 2026, 11:46 PM UTC): 🎉 The issue affecting Dashboard login has been resolved. All Cohere services are operating normally. Thank you for your patience while we worked through this.
/audio/transcriptions endpoint returns error for audio files with unexpected sampling rateAll systems operational
Jun 1, 2026, 1:51 PM UTC to Jun 1, 2026, 4:46 PM UTC (2h 54m)resolved
their latest update (Jun 1, 2026, 4:46 PM UTC): 🎉 The issue has been resolved and we are back to normal.
Docs Platform Degraded PerformanceMajor outage
Apr 20, 2026, 10:16 PM UTC to Apr 20, 2026, 10:28 PM UTC (13 min)resolved
their latest update (Apr 20, 2026, 10:28 PM UTC): Docs are back up!
Multiple Model DisruptionsMinor incident
Apr 13, 2026, 7:36 PM UTC to Apr 13, 2026, 9:00 PM UTC (1h 25m)resolved
their latest update (Apr 13, 2026, 9:00 PM UTC): 🎉 The issue has been resolved and we are back to normal.
Scheduled DB Maintenance: Model authentication and API access momentarily affectedMinor incident
Apr 11, 2026, 3:31 PM UTC to Apr 11, 2026, 3:39 PM UTC (9 min)resolved
their latest update (Apr 11, 2026, 3:39 PM UTC): 🎉 The issue has been resolved and we are back to normal.
Some chat models are unresponsive or timing outPartial outage
Feb 13, 2026, 4:34 AM UTC to Feb 13, 2026, 5:51 AM UTC (1h 18m)resolved
their latest update (Feb 13, 2026, 5:51 AM UTC): The issue has been resolved and all models are back to normal operation
Chat models return 503 service error when /v1/chat requests omit message and chat_history while providing tool_resultsAll systems operational
Oct 18, 2025, 9:46 PM UTC to Oct 18, 2025, 10:23 PM UTC (37 min)resolved
their latest update (Oct 18, 2025, 10:23 PM UTC): 🎉 The issue has been resolved and we are back to normal.
logprobs param degeraded for `command-a-03-2025` and `command-a-reasoning-08-2025`Minor incident
Oct 1, 2025, 3:56 PM UTC to Oct 1, 2025, 7:46 PM UTC (3h 50m)resolved
their latest update (Oct 1, 2025, 7:46 PM UTC): `logprobs` feature has been correctly marked as unavailable for the specified models.

Showing the 10 most recent of 26 incidents Cohere has declared in the history we hold.

These entries are Cohere's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Cohere's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Cohere's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Cohere since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Cohere decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Cohere believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.