Some initial queries to infrequently read namespaces incorrectly returning empty results
Jun 18, 10:00 UTCJun 18, 18:23 UTC
Duration
8h 23m
Impact
Minor
Root cause
Not disclosed
Pinecone, 90 days
8 incidents
Affected
AWS us-west-2AWS eu-west-1Azure eastus2GCP us-central1GCP europe-west4Serverless Indexes - AWS us-west-2Serverless Indexes - AWS eu-west-1Serverless Indexes - Azure eastus2Serverless Indexes - GCP us-central1Serverless Indexes - GCP europe-west4
Final update
This incident has been resolved.
Timeline
- Resolved · Jun 18, 18:23 UTC
This incident has been resolved.
- Investigating · Jun 18, 10:00 UTC
We are currently investigating this issue.
More from Pinecone
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2223:34 UTC | [Serverless][AWS][eu-west-1] 5xx on read requests | major | 58m |
| Sep 1705:37 UTC | [Serverless][AWS][us-west-2] 5xx errors on the readpath | major | 11h 7m |
| Sep 115:04 UTC | 5xx errors on some control plane operations | major | 4h 36m |
| Aug 2515:50 UTC | [SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests | major | 21m |
| Jul 2119:10 UTC | [SERVERLESS][Azure][eastus2] 5xx errors for some namespaces | critical | 30m |
| Jul 2016:44 UTC | [SERVERLESS][AWS][us-east-1] Increased latency and 5xx errors for some indexes | minor | 1h 15m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.