Pinecone outage, 2 November 2026

[Pod-Based Indexes] Stalled control plane operations.

Started
Status
Ongoing: Identified
Impact
Minor
Affected
Index Management

Is this still happening?

Yes. Pinecone still lists it as identified; last update 2 Nov 2026, 21:29 UTC.

Right now: Pinecone reports degraded performance on some systems. (as of 2 Nov, 23:28 UTC) Live Pinecone status

Last update from Pinecone

We are continuing to work on a fix for this issue.

2 Nov 2026, 21:29 UTC

Read the full incident on the official Pinecone status page

Similar Pinecone incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 4 h 36 min

    5xx errors on some control plane operations

  2. , resolved after 1 h 9 min

    [SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize

  3. , resolved after 2 h 44 min

    [Serverless][AWS][us-west-2] Read path operations for some indexes may experience elevated latency and timeouts

  4. , resolved after 1 h 1 min

    [AWS][us-east-1] 5xx errors on read and write operations for some indexes

  5. , resolved after 1 h 3 min

    [GCP][europe-west4] Errors for upsert operations on some indexes

Other recent Pinecone incidents

  1. [Inference] 5xx errors on some `llama-text-embed-v2` requests

  2. [Pods][AWS][us-east-1] Write failures and high latency

  3. [Serverless][AWS][eu-west-1] 5xx on read requests

  4. [Serverless][AWS][us-west-2] 5xx errors on the readpath

  5. [SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests

  6. [SERVERLESS][Azure][eastus2] 5xx errors for some namespaces

  7. [SERVERLESS][AWS][us-east-1] Increased latency and 5xx errors for some indexes

  8. [Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces

All recorded Pinecone incidents