Pinecone outage, 10 November 2026
[Serverless][GCP][us-central1] Elevated errors and timeouts on read operations for some indexes
- Started
- Resolved
- 10 Nov 2026, 18:44 UTC (after 1 h 54 min)
- Impact
- Major
- Affected
- GCP us-central1
Is this still happening?
No. Pinecone marked this incident resolved on 10 Nov 2026, 18:44 UTC, 1 h 54 min after it began.
Right now: Pinecone reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Pinecone status
At a glance
- Pinecone rated this a major incident (partial outage).
- It was resolved after 1 h 54 min. That is longer than a typical Pinecone incident: the median of the 26 other resolved ones we recorded is 1 h 18 min.
- Pinecone had 3 other incidents in the 30 days before it.
- 5 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 7 Oct 2026.
- Pinecone has not posted a root cause analysis on its status page.
Our summary from the Pinecone incidents we have recorded since 5 Feb 2026 - how we count.
Last update from Pinecone
This incident has been resolved.
Similar Pinecone incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 1 h 10 min
[Serverless][GCP][us-central1] 5xx errors on some read operations for some indexes
-
, resolved after 21 min
[SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests
-
, resolved after 2 h 38 min
[GCP][us-central1][europe-west4] Errors on some read operations
-
, resolved after 2 h 44 min
-
, resolved after 1 h 9 min
[SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize
Other recent Pinecone incidents
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.