">
sevanalysis

Pinecone

AI. Source: Pinecone status page.

Incidents, last 90 days
7
Median to mitigation
31m
Median to resolution
58m
p95 to resolution
11h 7m
Naming an upstream provider
85%
With a postmortem on the status page
0%

What failed, last 90 days

A zone, region or data center became unavailable4
A provider or third-party service this vendor depends on failed2
The text does not say enough to tell1

Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.

Incidents per month

All recorded incidents

[Inference] 5xx errors on some `llama-text-embed-v2` requests minor 2026-10-14 14:48 UTC 0m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. resolved

    Incident is resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize major 2026-10-07 20:40 UTC 1h 10m

Affected: Index Management

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Pods][AWS][us-east-1] Write failures and high latency minor 2026-09-28 04:07 UTC 14m

Affected: us-east-1-aws

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. identified

    A shared dependency is having issues. Determining mitigation

  2. resolved

    The third party dependency recovered, this incident has resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][eu-west-1] 5xx on read requests major 2026-09-22 23:34 UTC 58m

Affected: AWS eu-west-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. identified

    The issue has been identified and mitigation is being actioned. A small percentage of read requests are impacted.

  2. monitoring

    We have mitigated the errors and are monitoring to ensure there is no reoccurrence.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-west-2] 5xx errors on the readpath major 2026-09-17 05:37 UTC 11h 7m

Affected: AWS us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We have identified the issue and we are in the process of mitigating.

  2. monitoring

    We are recovering and are monitoring to ensure no further errors occur.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

5xx errors on some control plane operations major 2026-09-01 15:04 UTC 4h 36m

Affected: Console, Index Management, Assistant

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

  1. investigating

    We are currently investigating this issue.

  2. investigating

    This is likely related to ongoing issues in GCP. Affected services include Console, Index management, Assistant management, and APIs served at api.pinecone.io

  3. monitoring

    Error rates have subsided, we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests major 2026-08-25 15:50 UTC 21m

Affected: GCP us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[SERVERLESS][Azure][eastus2] 5xx errors for some namespaces critical 2026-07-21 19:10 UTC 30m

Affected: Azure eastus2

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[SERVERLESS][AWS][us-east-1] Increased latency and 5xx errors for some indexes minor 2026-07-20 16:44 UTC 1h 15m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces minor 2026-07-12 23:21 UTC 4h 55m

Affected: AWS us-east-1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are observing freshness lag affecting a small number of indexes in AWS us-east-1, resulting in some queries not serving fresh data. We are actively investigating.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][Azure][eastus2] 5xx errors on some requests for some indexes major 2026-07-09 09:50 UTC 4h 47m

Affected: Azure eastus2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Some initial queries to infrequently read namespaces incorrectly returning empty results minor 2026-06-18 10:00 UTC 8h 23m

Affected: AWS us-west-2, AWS eu-west-1, Azure eastus2, GCP us-central1, GCP europe-west4

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] Metrics tab in the console not showing graphs none 2026-06-16 13:05 UTC 4h

Affected: AWS us-east-1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-west-2] 5xx errors for some requests on some indexes major 2026-06-06 17:05 UTC 3h 35m

Affected: AWS us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-west-2] Read path operations for some indexes may experience elevated latency and timeouts minor 2026-06-06 13:05 UTC 2h 45m

Affected: AWS us-west-2

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[AWS][us-east-1] 5xx errors for some requests on some indexes minor 2026-06-06 00:48 UTC 27m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. investigating

    We are continuing to investigate this issue.

  3. identified

    The issue has been identified and a fix is being implemented.

  4. monitoring

    A fix has been implemented and we are monitoring the results.

  5. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-west-2] 5xx errors and longer response times on upsert requests for some indexes. major 2026-05-25 13:41 UTC 1h 19m

Affected: AWS us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[AWS][us-east-1] 5xx errors on read and write operations for some indexes major 2026-05-13 20:14 UTC 1h 1m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[AWS][us-east-1] 5xx errors for some requests on some indexes major 2026-05-06 20:02 UTC 27m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Pinecone Console loading slowly for some users minor 2026-05-06 15:00 UTC 20m

Affected: Console

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    The hosting provider for app.pinecone.io experienced increased errors and latency starting at 15:00 UTC. At 15:15 UTC, they implemented a fix and are continuing to monitor the impact. This incident did not impact Pinecone APIs or services.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[GCP][europe-west4] Errors for upsert operations on some indexes major 2026-03-13 08:50 UTC 1h 3m

Affected: GCP europe-west4

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[AWS][us-east-1] Prometheus metrics are unavailable through the Pinecone console or the metric proxy minor 2026-03-05 21:57 UTC 1h 5m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][GCP][us-central1] 5xx errors on some read operations for some indexes major 2026-03-04 21:06 UTC 1h 10m

Affected: GCP us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[GCP][us-central1][europe-west4] Errors on some read operations major 2026-02-23 23:14 UTC 2h 38m

Affected: GCP us-central1, GCP europe-west4

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    The impact was related to a Google Cloud Storage incident (Event ID: WDVVRMB).

  3. identified

    The issue has been identified and a fix is being implemented.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces minor 2026-02-05 10:55 UTC 11h 2m

Affected: AWS us-east-1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes major 2026-01-15 12:12 UTC 3h 18m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Intermittent unavailability across all environments for some indexes major 2026-01-02 16:31 UTC 1h 27m

Affected: us-west1-gcp, Console, AWS us-west-2, us-east1-gcp, AWS us-east-1, us-central1-gcp, AWS eu-west-1, us-west4-gcp, Azure eastus2, us-east4-gcp, GCP us-central1, us-west1-gcp-free, GCP europe-west4, us-west4-gcp-free, gcp-starter, eu-west1-gcp, eu-west4-gcp, asia-southeast1-gcp, asia-northeast1-gcp, asia-southeast1-gcp-free, Index Management, northamerica-northeast1-gcp, Inference, eastus-azure, Assistant, us-east-1-aws

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-west-2] 5xx errors on some read path operations major 2025-12-31 03:13 UTC 16m

Affected: AWS us-west-2

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][GCP][us-central1] Partial control plane unavailability for some users none 2025-12-19 01:15 UTC 0m

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. resolved

    From 8:15 PM to 8:50 PM UTC, some users experienced partial control plane unavailability.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][GCP][europe-west4] 5xx errors on read and write operations for some indexes major 2025-12-15 10:39 UTC 11h 23m

Affected: GCP europe-west4

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Increased file processing time for Assistant minor 2025-12-09 20:15 UTC 5h 35m

Affected: Assistant

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

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

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Unavailability for embed and rerank requests none 2025-12-08 20:43 UTC 0m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. resolved

    From 3:43 PM EST to 3:50 PM EST, some embed and rerank requests were unavailable.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][GCP][us-central1] 5xx errors on some read operations for some namespaces major 2025-12-05 18:36 UTC 2h 6m

Affected: GCP us-central1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-west-2] 5xx errors on read path operations for some namespaces major 2025-12-03 15:53 UTC 46m

Affected: AWS us-west-2

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] 5xx errors on some read path operations major 2025-11-24 17:28 UTC 1h 2m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Some index-level usage metrics unavailable none 2025-11-13 02:00 UTC 0m

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. resolved

    Index-level usage metrics were unavailable for approximately 24 hours beginning at around 9:00 PM EST on November 12th

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][eu-west-1] 5xx errors on some write path operations major 2025-11-06 14:38 UTC 2m

Affected: AWS eu-west-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Partial unavailability on cohere-rerank-3.5 model none 2025-10-30 22:00 UTC 0m

Affected: Inference

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. resolved

    From 4:58 PM EST to 5:10 PM EST, the cohere-rerank-3.5 model experienced partial unavailability.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][GCP][us-central1] 5xx errors on some read and write operations major 2025-10-23 17:32 UTC 51m

Affected: GCP us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. investigating

    We are continuing to investigate this issue.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][Azure][eastus2] 5xx errors on some read and write operations major 2025-10-21 17:57 UTC 1h 27m

Affected: Azure eastus2

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Some users may be unable to access the Pinecone web console. All API services remain fully operational. major 2025-10-21 01:27 UTC 2h 3m

Affected: Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Some users may be unable to access the Pinecone web console. All API services remain fully operational. major 2025-10-20 17:05 UTC 55m

Affected: Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] `403 PermissionDenied` errors for read and write operations on some indexes and assistants minor 2025-09-15 15:52 UTC 6m

Affected: AWS us-east-1

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. monitoring

    A fix has been implemented and we are monitoring the results.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] 5xx errors on some read and write operations major 2025-09-10 13:16 UTC 3h 22m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-west-2] 5xx errors on some read operations major 2025-09-10 12:52 UTC 4h 30m

Affected: AWS us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] 5xx errors on write operations for some indexes major 2025-09-09 12:55 UTC 1h 45m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes major 2025-09-02 22:46 UTC 15h 14m

Affected: AWS us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

Console stuck loading after login for some users minor 2025-08-29 20:28 UTC 2h 14m

Affected: Console

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. investigating

    We are investigating an issue where some users are unable to access the console after logging in. Affected users may see the console stuck in a loading state. The issue is related to elevated errors from our authentication provider.

  2. monitoring

    The loading issue has recovered, and we are continuing to monitor.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][AWS][us-west-2] Unavailability for some read path operations for some indexes major 2025-08-28 18:30 UTC 1h 55m

Affected: AWS us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.

[Serverless][GCP][europe-west4] Indexing lag on some indexes; recent writes may not appear in reads minor 2025-08-26 13:22 UTC 1h 43m

Affected: GCP europe-west4

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Pinecone's status page.