[Serverless][Azure][eastus2] 5xx errors for some requests on some indexes
Timeline · 1 update
- investigating Jul 09, 2026, 01:34 PM UTC
We are currently investigating this issue.
Pinecone had 44 outages in the last 2 years totaling 74h 17m of downtime — averaging 1.8 incidents per month.
There were 44 Pinecone outages since June 22, 2025 totaling 74h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
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.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The impact was related to a Google Cloud Storage incident (Event ID: WDVVRMB).
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
From 8:15 PM to 8:50 PM UTC, some users experienced partial control plane unavailability.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Files uploaded to an assistant may take longer than expected to appear in chat and context requests during this time.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
From 3:43 PM EST to 3:50 PM EST, some embed and rerank requests were unavailable.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.