outages.live
Live
CohereIncident · 2026-08-05 19:36 UTC

Documentation Content Loading Issues

ResolvedOfficial update

🎉 The issue has been resolved and we are back to normal.

The latest update from Cohere.

State

Resolved

Started

88 d ago

2026-08-05 19:36 UTC

Lasted

57 min

until 2026-08-05 20:33 UTC

Worst impact

Partial outage

Timeline

3 updates
19:3619:5020:0420:1920:33
Partial outageUpdate postedTimes in UTC

Investigating

57 min 100%

Updates

Times in UTC

As posted by Cohere

Resolved2026-08-05 20:35 UTC

🎉 The issue has been resolved and we are back to normal.

Resolved2026-08-05 20:33 UTC

🎉 The issue has been resolved and we are back to normal.

Investigating2026-08-05 19:36 UTC

We are investigating a partial outage affecting our documentation site. Some documentation pages may not load correctly due to an ongoing issue with our upstream documentation provider (Fern). We are monitoring the incident and will share updates as they become available.

Cohere in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

2 h 40 min

This incident

64% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 22 min
median 2 h 40 min
90 days agoToday

Other Cohere incidents

All incidents

Cohere·Multiple Endpoint Disruptions

🎉 The issue has been resolved and we are back to normal.

Resolvedresolved 61 d ago

Follow Cohere

Your coding agent knows when Cohere is down, and tells you when a failure is theirs, not yours. You can also get Cohere incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cohere" and tell me if Cohere has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=cohere
Slack
/feed subscribe https://outages.live/feed.xml?providers=cohere

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane