Companies / Pinecone / changes

Pinecone change history

31Major incident
When (UTC)ChangeKind
Major incident: [SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize
Newly created Pinecone serverless indexes on GCP in us-central1 failed to initialize, affecting Index Management. The vendor rated the incident major; it began at 2026-10-07 20:40 UTC and was resolved at 2026-10-07 21:49 UTC, lasting 1 h 9 min. No cause or fix was stated.
Major incident
Major incident: [Serverless][AWS][eu-west-1] 5xx on read requests
Pinecone reported a major incident affecting a small percentage of Serverless read requests in AWS eu-west-1 with 5xx errors. It started at 2026-09-22 23:34 UTC and was resolved at 2026-09-23 00:32 UTC, lasting 57 min. Pinecone reported mitigating the errors at 2026-09-23 00:05 UTC.
Major incident
Major incident: [Serverless][AWS][us-west-2] 5xx errors on the readpath
Pinecone reported a major incident causing readpath 5xx errors for Serverless Indexes in AWS us-west-2, from 2026-09-17 05:37 UTC to 2026-09-17 16:44 UTC (11 h 7 min). Pinecone reported mitigation underway, followed by recovery monitoring and resolution; no specific cause or fix was stated.
Major incident
Major incident: 5xx errors on some control plane operations
Pinecone reported a major incident causing 5xx errors on some control plane operations, affecting Console, Index management, Assistant management, and APIs at api.pinecone.io. It started at 2026-09-01 15:04 UTC and was resolved at 2026-09-01 19:40 UTC, lasting 4 h 36 min. Pinecone said it was likely related to ongoing GCP issues.
Major incident
Major incident: [SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests
Pinecone reported a major incident affecting Serverless Indexes in GCP us-central1, with 5xx errors on some read and write requests. It started at 2026-08-25 15:50 UTC and was resolved at 2026-08-25 16:11 UTC, lasting 21 min; Pinecone stated that a fix was implemented.
Major incident
Critical incident: [SERVERLESS][Azure][eastus2] 5xx errors for some namespaces
Pinecone reported a critical incident causing 5xx errors for some Serverless namespaces in Azure eastus2. It started at 2026-07-21 19:10 UTC and was resolved at 2026-07-21 19:40 UTC, with a reported duration of 29 min; Pinecone identified the issue and implemented a fix but did not specify the cause.
Major incident
Major incident: [Serverless][Azure][eastus2] 5xx errors on some requests for some indexes
Pinecone reported a major outage causing 5xx errors on some requests for some Serverless indexes in Azure eastus2. It started at 2026-07-09 09:50 UTC and was resolved at 2026-07-09 14:37 UTC, lasting 4 h 47 min; Pinecone reported implementing a fix and monitoring the results.
Major incident
Major incident: [Serverless][AWS][us-west-2] 5xx errors for some requests on some indexes
Pinecone reported a major outage causing 5xx errors for some requests on some Serverless indexes in AWS us-west-2. It started at 2026-06-06 17:05 UTC and was resolved at 2026-06-06 20:40 UTC, lasting 3 h 35 min; no cause or fix was stated.
Major incident
Major incident: [Serverless][AWS][us-west-2] 5xx errors and longer response times on upsert requests for some indexes.
Pinecone reported a major incident causing 5xx errors and longer response times for upsert requests on some Serverless indexes in AWS us-west-2. It started at 2026-05-25 13:41 UTC and was resolved at 2026-05-25 15:00 UTC, lasting 1 h 18 min. A fix was implemented, but no cause was stated.
Major incident
Major incident: [AWS][us-east-1] 5xx errors on read and write operations for some indexes
Some Pinecone indexes in AWS us-east-1 experienced 5xx errors on read and write operations, affecting Serverless Indexes. Pinecone rated the incident major; it started at 2026-05-13 20:14 UTC and was resolved at 2026-05-13 21:15 UTC, lasting 1 h 1 min. Pinecone reported identifying the issue and implementing a fix but gave no cause or fix details.
Major incident
Major incident: [AWS][us-east-1] 5xx errors for some requests on some indexes
Pinecone reported a major incident affecting AWS us-east-1 Serverless Indexes, with 5xx errors for some requests on some indexes. It started at 2026-05-06 20:02 UTC and was resolved at 2026-05-06 20:30 UTC, lasting 27 min. A fix was implemented by 05-06 20:14 UTC; no cause was stated.
Major incident
Major incident: [GCP][europe-west4] Errors for upsert operations on some indexes
Pinecone reported a major incident causing upsert errors on some indexes in GCP europe-west4, affecting Serverless Indexes. It started at 2026-03-13 08:50 UTC and was resolved at 2026-03-13 09:53 UTC, lasting 1 h 3 min; a fix was implemented and monitored before resolution.
Major incident
Major incident: [Serverless][GCP][us-central1] 5xx errors on some read operations for some indexes
Pinecone reported a major incident causing 5xx errors on some read operations for some Serverless indexes in GCP us-central1. It started at 2026-03-04 21:06 UTC and was resolved at 2026-03-04 22:16 UTC, lasting 1 h 10 min. A fix was implemented; affected customers could encounter failed reads during the incident.
Major incident
Major incident: [GCP][us-central1][europe-west4] Errors on some read operations
Pinecone reported a major incident causing errors on some read operations for Serverless Indexes in GCP us-central1 and europe-west4. It started at 2026-02-23 23:14 UTC and was resolved at 2026-02-24 01:52 UTC, lasting 2 h 38 min. Pinecone linked the impact to a Google Cloud Storage incident (Event ID: WDVVRMB) and reported implementing a fix.
Major incident
Major incident: [Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes
Pinecone reported a major incident causing 5xx errors on read operations for some Serverless indexes in AWS us-east-1. It started at 2026-01-15 12:12 UTC and was resolved at 2026-01-15 15:30 UTC, lasting 3 h 18 min. A fix was implemented by 2026-01-15 14:30 UTC; no cause was stated.
Major incident
Major incident: Intermittent unavailability across all environments for some indexes
Pinecone reported a major incident causing intermittent unavailability for some indexes across all environments, starting at 2026-01-02 16:31 UTC. A fix was implemented by 01-02 17:18 UTC, and the incident was resolved at 2026-01-02 17:58 UTC; the reported duration was 1 h 26 min.
Major incident
Major incident: [Serverless][AWS][us-west-2] 5xx errors on some read path operations
Pinecone reported a major incident causing 5xx errors on some Serverless read-path operations in AWS us-west-2. It started at 2025-12-31 03:13 UTC and was resolved at 2025-12-31 03:29 UTC, lasting 16 min; a fix was implemented, but no cause was stated.
Major incident
Major incident: [Serverless][GCP][europe-west4] 5xx errors on read and write operations for some indexes
Pinecone reported a major outage causing 5xx errors on read and write operations for some Serverless indexes in GCP europe-west4. It started at 2025-12-15 10:39 UTC and was resolved at 2025-12-15 22:02 UTC, lasting 11 h 22 min; a fix was implemented, but no cause was stated.
Major incident
Major incident: [Serverless][GCP][us-central1] 5xx errors on some read operations for some namespaces
Pinecone reported a major incident affecting Serverless Indexes in GCP us-central1, with 5xx errors on some read operations for some namespaces. It ran from 2025-12-05 18:36 UTC to 2025-12-05 20:42 UTC, lasting 2 h 6 min. A fix was implemented by 20:01 UTC; no cause was stated.
Major incident
Major incident: [Serverless][AWS][us-west-2] 5xx errors on read path operations for some namespaces
Pinecone reported a major incident causing 5xx errors on read-path operations for some Serverless namespaces in AWS us-west-2, affecting customer reads. It started at 2025-12-03 15:53 UTC and was resolved at 2025-12-03 16:40 UTC, lasting 46 min; Pinecone implemented a fix but did not state a cause.
Major incident
Major incident: [Serverless][AWS][us-east-1] 5xx errors on some read path operations
Pinecone reported a major incident causing 5xx errors on some read path operations for Serverless Indexes in AWS us-east-1. It started at 2025-11-24 17:28 UTC and was resolved at 2025-11-24 18:30 UTC, lasting 1 h 1 min. Pinecone reported implementing a fix and monitoring the results before resolution; no cause was stated.
Major incident
Major incident: [Serverless][AWS][eu-west-1] 5xx errors on some write path operations
Pinecone reported a major incident causing 5xx errors on some Serverless write path operations in AWS eu-west-1, affecting customers writing to indexes in that region. It started at 2025-11-06 14:38 UTC and was resolved at 2025-11-06 14:40 UTC, lasting 2 min; no cause or fix was stated.
Major incident
Major incident: [Serverless][GCP][us-central1] 5xx errors on some read and write operations
Pinecone reported a major incident causing 5xx errors on some read and write operations for Serverless Indexes in GCP us-central1, starting 2025-10-23 17:32 UTC. A fix was implemented at 17:42 UTC, and the incident was resolved at 2025-10-23 18:23 UTC after 51 min.
Major incident
Major incident: [Serverless][Azure][eastus2] 5xx errors on some read and write operations
Pinecone reported a major incident affecting Serverless Indexes in Azure eastus2, with 5xx errors on some read and write operations. It started at 2025-10-21 17:57 UTC and resolved at 2025-10-21 19:24 UTC, lasting 1 h 26 min. A fix was implemented; no cause was stated.
Major incident
Major incident: Some users may be unable to access the Pinecone web console. All API services remain fully operational.
Some users were unable to access the Pinecone web console during a major-impact incident from 2025-10-21 01:27 UTC to 2025-10-21 03:30 UTC, lasting 2 h 3 min. All API services remained fully operational; Pinecone reported implementing a fix at 10-21 02:20 UTC and subsequently resolved the incident.
Major incident
Major incident: Some users may be unable to access the Pinecone web console. All API services remain fully operational.
Some users could not access Pinecone’s web console during a major-impact outage; all API services remained fully operational. The incident started at 2025-10-20 17:43 UTC and was resolved at 2025-10-20 18:00 UTC, lasting 16 min. Pinecone reported implementing a fix and monitoring the results.
Major incident
Major incident: [Serverless][AWS][us-east-1] 5xx errors on some read and write operations
Pinecone reported a major outage causing 5xx errors on some Serverless read and write operations in AWS us-east-1. It started at 2025-09-10 13:16 UTC and was resolved at 2025-09-10 16:38 UTC, lasting 3 h 21 min. A fix was implemented at 13:22 UTC; no cause was stated.
Major incident
Major incident: [Serverless][AWS][us-west-2] 5xx errors on some read operations
Pinecone reported a major incident causing 5xx errors on some Serverless read operations in AWS us-west-2, from 2025-09-10 12:52 UTC to 2025-09-10 17:22 UTC (4 h 30 min). A fix was implemented by 2025-09-10 13:16 UTC, followed by monitoring and resolution.
Major incident
Major incident: [Serverless][AWS][us-east-1] 5xx errors on write operations for some indexes
Pinecone reported a major incident causing 5xx errors on write operations for some Serverless indexes in AWS us-east-1. It started at 2025-09-09 12:55 UTC and was resolved at 2025-09-09 14:40 UTC, lasting 1 h 44 min; a fix was implemented at 09-09 13:43 UTC.
Major incident
Major incident: [Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes
Pinecone reported a major incident affecting Serverless indexes in AWS us-east-1, with 5xx errors on read operations for some indexes. It started at 2025-09-02 22:46 UTC and was resolved at 2025-09-03 14:00 UTC, lasting 15 h 14 min. Pinecone stated that a fix was implemented and monitored before resolution.
Major incident
Major incident: [Serverless][AWS][us-west-2] Unavailability for some read path operations for some indexes
Pinecone reported a major outage affecting some read-path operations for some Serverless indexes in AWS us-west-2, starting 2025-08-28 18:30 UTC and lasting 1 h 54 min. A fix was implemented by 2025-08-28 20:18 UTC, and the incident was resolved at 2025-08-28 20:25 UTC.
Major incident