Vendor Status Watch

← all vendors

Cohere status history

Current state: operational — “All Systems Operational” per https://status.cohere.ai (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
3incidents, last 90 days
10incidents on record
Incidents per week, last 12 weeks:
Get Cohere alerts in your Slack — free templateRSS for Cohere

How long do Cohere incidents last?

67 minmedian incident duration10 measured
3.8 h90th percentile1 in 10 ran longer
53 minmedian, major/critical only4 incidents

From 10 incidents with a vendor-posted start and resolve time. Longest on record: Multiple Endpoint Disruptions — 4.4 h (2026-09-01 15:41 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (10)

StartedIncidentStatusImpactDuration
2026-09-01 15:41 UTCMultiple Endpoint Disruptionsresolvedminor4 h 22 min
2026-08-05 19:36 UTCDocumentation Content Loading Issuesresolvedmajor57 min
2026-07-23 22:56 UTCDashboard Login Service Disruptionresolvedmajor50 min
2026-06-01 13:51 UTC/audio/transcriptions endpoint returns error for audio files with unexpected sampling rateresolvednone2 h 54 min
2026-04-20 22:16 UTCDocs Platform Degraded Performanceresolvedcritical12 min
2026-04-13 19:36 UTCMultiple Model Disruptionsresolvedminor1 h 24 min
2026-04-11 15:31 UTCScheduled DB Maintenance: Model authentication and API access momentarily affectedresolvedminor8 min
2026-02-13 04:34 UTCSome chat models are unresponsive or timing outresolvedmajor1 h 17 min
2025-10-18 21:46 UTCChat models return 503 service error when /v1/chat requests omit message and chat_history while providing tool_resultsresolvednone36 min
2025-10-01 15:56 UTClogprobs param degeraded for `command-a-03-2025` and `command-a-reasoning-08-2025`resolvedminor3 h 49 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Cohere with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "cohere"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}