Official incident history

  1. Started: · Duration: 262 min
    Provider updates (4)
    1. Investigating “🔎 We are currently investigating this live incident.”
    2. Identified “🛠️ 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"))”
    3. Monitoring “👀 We are monitoring to make sure the incident has been fully resolved.”
    4. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  2. Started: · Duration: 57 min
    Provider updates (2)
    1. Investigating “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.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  3. Started: · Duration: 51 min
    Provider updates (4)
    1. Investigating “🔎 We are currently investigating an issue affecting the Cohere Dashboard ([dashboard.cohere.com](http://dashboard.cohere.com "dashboard.cohere.com")). Users may experience a continuous refresh loop on the login page, preventing successful authentication.”
    2. Identified “🛠️ **Update:** We have identified the cause of login issues affecting the Cohere Dashboard, preventing successful logins. A fix is being implemented now and we expect Dashboard login to be restored shortly. **Note:** API access, model inference, and all other Cohere services are **unaffected** and operating normally.”
    3. Monitoring “👀 The issue affecting Dashboard login has been resolved ✅. We're monitoring to confirm stability. All Cohere services are operating normally.”
    4. Resolved “🎉 The issue affecting Dashboard login has been resolved. All Cohere services are operating normally. Thank you for your patience while we worked through this.”
    Resolved
  4. Started: · Duration: 174 min
    Provider updates (2)
    1. Identified “/audio/transcriptions endpoints availability is affected now due to the Cohere ASR model backing the endpoint throws error for any audio inputs that are in the expected sampling rate. Previously these sampling rate audio files were accepted and processed, marking this as a regression type incident. :hammer_and_wrench: We have identified the root cause of the incident, and are working diligently…”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  5. Cohere: degraded performance

    Provider's original title: Docs Platform Degraded Performance

    Started: · Duration: 13 min
    Provider updates (2)
    1. Investigating “We are currently experiencing an outage affecting our documentation site due to an issue with our third-party documentation provider, Fern. Our team is actively monitoring the situation while the provider investigates and works on a fix.”
    2. Resolved “Docs are back up!”
    Resolved
  6. Started: · Duration: 85 min
    Provider updates (3)
    1. Investigating “We are currently investigating Multiple Model Disruptions.”
    2. Monitoring “👀 We are monitoring to make sure the incident has been fully resolved.”
    3. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  7. Cohere: API, sign-in, scheduled maintenance

    Provider's original title: Scheduled DB Maintenance: Model authentication and API access momentarily affected

    Started: · Duration: 9 min
    Provider updates (2)
    1. Identified “There is a scheduled DB maintenance in progress. All the API authentication when accessing models are affected momentarily. The auth and API services is coming back online and should be fully up very soon.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  8. Started: · Duration: 78 min
    Provider updates (3)
    1. Investigating “We are currently investigating an incident with chat models. ”
    2. Monitoring “We identified and resolved the connectivity problem affecting certain chat models. Affected models are starting to come back online.”
    3. Resolved “The issue has been resolved and all models are back to normal operation”
    Resolved
  9. Started: · Duration: 37 min
    Provider updates (2)
    1. Identified “🛠️ We have identified the root cause of the incident, and are working diligently to fix.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  10. Started: · Duration: 230 min
    Provider updates (2)
    1. Investigating “We have identified that the `logprobs` parameter is not working as expected for the following models: - `command-a-03-2025` - `command-a-reasoning-08-2025` The team is investigating the incident.”
    2. Resolved “`logprobs` feature has been correctly marked as unavailable for the specified models.”
    Resolved
  11. Cohere: degraded performance

    Provider's original title: Command-a-vision-07-2025 degraded performance

    Started: · Duration: 10 min
    Provider updates (2)
    1. Identified “🛠️ We have identified the root cause of the incident, and are working diligently to fix.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  12. Cohere: outage or errors

    Provider's original title: Model serving infrastructure outage

    Started: · Duration: 237 min
    Provider updates (4)
    1. Investigating “Command models are down due to a model serving infrastructure outage”
    2. Identified “🛠️ We have identified the root cause of the incident, and are working diligently to fix.”
    3. Monitoring “👀 We are monitoring to make sure the incident has been fully resolved.”
    4. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  13. Cohere: outage or errors

    Provider's original title: GCP Outage

    Started: · Duration: 223 min
    Provider updates (2)
    1. Monitoring “We are currently experiencing an outage with Google Cloud Platform (GCP), which may impact some of our services. Our team is actively monitoring the situation.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  14. Cohere: degraded performance

    Provider's original title: Degraded service affecting embed-v4.0

    Started: · Duration: 142 min
    Provider updates (2)
    1. Investigating “🔎 We are currently investigating this live incident.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  15. Cohere: degraded performance

    Provider's original title: Degraded service affecting embedding models

    Started: · Duration: 7236 min
    Provider updates (3)
    1. Investigating “🔎 We are currently investigating this live incident.”
    2. Monitoring “👀 We are monitoring to make sure the incident has been fully resolved.”
    3. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  16. Started: · Duration: 1649 min
    Provider updates (4)
    1. Investigating “🔎 We are currently investigating this live incident.”
    2. Identified “🛠️ We have identified the root cause of the incident, and are working diligently to fix.”
    3. Monitoring “👀 We are monitoring to make sure the incident has been fully resolved.”
    4. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  17. Cohere: increased latency

    Provider's original title: Degraded Performance: command-a-03-2025 - Increased Latency

    Started: · Duration: 208 min
    Provider updates (2)
    1. Monitoring “👀 We are monitoring to make sure the incident has been fully resolved.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  18. Cohere: increased latency

    Provider's original title: High latency

    Started: · Duration: 11 min
    Provider updates (2)
    1. Investigating “🔎 We are currently investigating this live incident.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  19. Cohere: increased latency

    Provider's original title: Increased Latency

    Started: · Duration: 199 min
    Provider updates (2)
    1. Investigating “🔎 We are currently investigating this live incident.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved
  20. Cohere: increased latency

    Provider's original title: Increased Latency

    Started: · Duration: 21 min
    Provider updates (2)
    1. Investigating “🔎 We are currently investigating this live incident.”
    2. Resolved “🎉 The issue has been resolved and we are back to normal.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
Cohere Status ↗ · All Systems Operational · Nov 18, 10:26 PM UTC

Why this assessment

  • Provider reports no active incident.

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official2 min agoYes, recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗