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 unavailable | 4 |
| A provider or third-party service this vendor depends on failed | 2 |
| The text does not say enough to tell | 1 |
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
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).
-
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
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.
-
investigating
We are currently investigating this issue.
-
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
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.
-
identified
A shared dependency is having issues. Determining mitigation
-
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
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.
-
identified
The issue has been identified and mitigation is being actioned. A small percentage of read requests are impacted.
-
monitoring
We have mitigated the errors and are monitoring to ensure there is no reoccurrence.
-
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
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.
-
investigating
We have identified the issue and we are in the process of mitigating.
-
monitoring
We are recovering and are monitoring to ensure no further errors occur.
-
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
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..
-
investigating
We are currently investigating this issue.
-
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
-
monitoring
Error rates have subsided, we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
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
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.
-
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.
-
identified
The issue has been identified and a fix is being implemented.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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).
-
investigating
We are currently investigating this issue.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
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
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.
-
investigating
We are currently investigating this issue.
-
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
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.
-
investigating
We are currently investigating this issue.
-
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
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.
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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.
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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).
-
investigating
We are currently investigating this issue.
-
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.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
The impact was related to a Google Cloud Storage incident (Event ID: WDVVRMB).
-
identified
The issue has been identified and a fix is being implemented.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Pinecone's status page.
Increased file processing time for Assistant
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).
-
investigating
Files uploaded to an assistant may take longer than expected to appear in chat and context requests during this time.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Pinecone's status page.
Unavailability for embed and rerank requests
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).
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Pinecone's status page.
Some index-level usage metrics unavailable
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).
-
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
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.
-
investigating
We are currently investigating this issue.
-
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
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).
-
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
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.
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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.
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).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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.
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).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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).
-
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.
-
monitoring
The loading issue has recovered, and we are continuing to monitor.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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
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.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Pinecone's status page.