[Inference] 5xx errors on some `llama-text-embed-v2` requests
DegradedIncident is resolved.
Pinecone is up and running. Pinecone runs a hosted vector database for AI applications.
Worked out from the incidents Pinecone reported, so it is an estimate and not a measurement.
Last incident: “[Inference] 5xx errors on some `llama-text-embed-v2` requests”, 8 days ago.
Incident is resolved.
This incident has been resolved.
The third party dependency recovered, this incident has resolved.
This incident has been resolved.
This incident has been resolved.
Pinecone’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Pinecone reported was “[Inference] 5xx errors on some `llama-text-embed-v2` requests”, 8 days ago (2026-10-14 14:48 UTC). None of its incidents in the last 90 days were a full outage.
Pinecone reports 26 components on its status page, including us-west1-gcp, Console, AWS us-west-2, us-east1-gcp, AWS us-east-1. Each is checked again whenever this page refreshes.
Retry with exponential backoff, fall back to another model or provider if your product allows it, and avoid hammering the API while it recovers.
No — Pinecone lists indexes per cloud and region (AWS us-east-1, GCP us-central1, Azure…), and serverless vs pod indexes are separate rows. Match the row to where your index lives.
Possible — the status page lists free-tier environments separately (rows like 'us-west1-gcp-free'). Free-tier incidents don't imply paid regions are affected.
If the status above is operational but Pinecone still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.