[Serverless][GCP][us-central1] Elevated errors and timeouts on read operations for some indexes
Read operations failed with errors and timeouts on some serverless indexes in GCP us-central1. Pinecone reports that the incident is resolved. The incident lasted about 1 hour and 55 minutes.
State
Resolved
Started
Lasted
1 h 55 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
1 h 55 min 100%
Updates
Times in UTCAs posted by Pinecone
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Affected components
2Pinecone in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
11
Median duration
1 h 21 min
This incident
1.4× the median
Other Pinecone incidents
All incidentsPinecone·[Metrics Endpoint] 5xx Errors on */metrics/discovery
Pinecone reported 5xx errors on the /metrics/discovery endpoint. The Console and Index Management components were affected. Pinecone resolved the incident after 93 minutes.
Pinecone·[Pod-Based Indexes] Stalled control plane operations.
Pinecone reports that control plane operations stalled for pod-based indexes. The problem affected Index Management. A fix is in place. Pinecone reports that the incident is resolved. The incident lasted about 3 hours and 19 minutes.
Pinecone·[Inference] 5xx errors on some `llama-text-embed-v2` requests
Incident is resolved.
Pinecone·[SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize
This incident has been resolved.
Pinecone·[Pods][AWS][us-east-1] Write failures and high latency
The third party dependency recovered, this incident has resolved.
Follow Pinecone
Your coding agent knows when Pinecone is down, and tells you when a failure is theirs, not yours. You can also get Pinecone incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "pinecone" and tell me if Pinecone has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=pinecone/feed subscribe https://outages.live/feed.xml?providers=pineconeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane