- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Cohere. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 3h it lasted.
Anything that failed between 2025-04-03 17:29 UTC and 2025-04-04 20:58 UTC may need a replay.Subscribe to Cohere's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cohere works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cohere 5
- investigating
🔎 We are currently investigating this live incident.
provider
- identified
🛠️ We have identified the root cause of the incident, and are working diligently to fix.
provider
- monitoring
👀 We are monitoring to make sure the incident has been fully resolved.
provider
- resolved
🎉 The issue has been resolved and we are back to normal.
provider
- resolved
🎉 The issue has been resolved and we are back to normal.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e8e8a37530
Is Cohere still down?
No, this incident was resolved 2025-04-04 20:58 UTC. For Cohere's live state, see https://down.guide/cohere.
How long did it last?
1d 3h, from 2025-04-03 17:29 UTC to 2025-04-04 20:58 UTC, by the times Cohere posted.
What caused it?
Cohere hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cohere's official status page, https://status.cohere.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.