Cohere reported "Multiple Endpoint Disruptions" on its status page at 2026-09-01 15:41 UTC.

Cohere did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-09-01 15:41 UTC and ended at 2026-09-01 20:03 UTC. It lasted 4 h 22 min.

How do I get alerts for Cohere?

Subscribe to the Cohere live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Cohere. outages.live reads it every few minutes and keeps every update.

CohereIncident · 2026-09-01 15:41 UTC

Multiple Endpoint Disruptions

ResolvedOfficial update

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

The latest update from Cohere.

State

Resolved

Started

61 d ago

2026-09-01 15:41 UTC

Lasted

4 h 22 min

until 2026-09-01 20:03 UTC

Worst impact

Degraded

Timeline

4 updates

15:4116:4617:5218:5720:03

DegradedUpdate postedTimes in UTC

Investigating

40 min 15%

Identified

3 h 26 min 79%

Monitoring

16 min 6%

Updates

Times in UTC

As posted by Cohere

Resolved2026-09-01 20:03 UTC

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

Monitoring2026-09-01 19:47 UTC

👀 We are monitoring to make sure the incident has been fully resolved.

Identified2026-09-01 16:21 UTC

🛠️ We have identified the root cause as an ongoing Google Cloud Platform (GCP) outage. Our team is actively monitoring the situation while we wait for GCP to resolve the underlying issue. ([reference](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "reference"))

Investigating2026-09-01 15:41 UTC

🔎 We are currently investigating this live incident.

Cohere in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 40 min

This incident

1.6× 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·Documentation Content Loading Issues

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

Resolvedresolved 88 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