Looking for an update now? Check the current status, or follow Pinecone for future changes.
89.7%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
83.3%
30
5
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
[SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize
Error rates have subsided, we are monitoring the results.
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
12 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
[SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests
majorSource not attested
Last archived state: resolved
View archived record details
GCP us-central1
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
July 2026
[SERVERLESS][Azure][eastus2] 5xx errors for some namespaces
criticalSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
[SERVERLESS][Azure][eastus2] 5xx errors for some namespaces
Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue.
[SERVERLESS][AWS][us-east-1] Increased latency and 5xx errors for some indexes
minorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
[Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces
minorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
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.
[Serverless][Azure][eastus2] 5xx errors for some requests on some indexes
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue.
June 2026
[Serverless][AWS][us-east-1] Metrics tab in the console not showing graphs
Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
[AWS][us-east-1] 5xx errors for some requests on some indexes
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
May 2026
[Serverless][AWS][us-west-2] 5xx errors and longer response times on upsert requests for some indexes.
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue.
[AWS][us-east-1] 5xx errors on read and write operations for some indexes
majorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.