Cohere vs. Pinecone

Compare the status, incidents stats and history between Cohere and Pinecone

Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.

Cohere

Cohere current official status is Operational

Statistics

0
Incidents in the last 7 days
0
Incidents in the last 30 days
2
Incidents in the last 90 days

Latest incidents

Resolved Chat models return 503 service error when /v1/chat requests omit message and chat_history while providing tool_results

🛠️ We have identified the root cause of the incident, and are working diligently to fix.

about 2 months ago Official incident report
Resolved logprobs param degeraded for `command-a-03-2025` and `command-a-reasoning-08-2025`

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.

Resolved Command-a-vision-07-2025 degraded performance

🛠️ We have identified the root cause of the incident, and are working diligently to fix.

Pinecone

Pinecone current official status is Operational

Statistics

2
Incidents in the last 7 days
4
Incidents in the last 30 days
8
Incidents in the last 90 days

Latest incidents

Resolved Increased file processing time for Assistant

Files uploaded to an assistant may take longer than expected to appear in chat and context requests during this time.

Resolved [Serverless][GCP][us-central1] 5xx errors on some read operations for some namespaces

We are currently investigating this issue.

Resolved [Serverless][AWS][us-west-2] 5xx errors on read path operations for some namespaces

We are currently investigating this issue.

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required