Pinecone reported "[Serverless][AWS][eu-west-1] 5xx on read requests" on its status page at 2026-09-22 23:34 UTC.

Pinecone lists these components: AWS eu-west-1, Serverless Indexes - AWS eu-west-1.

When did the incident start and end?

It started at 2026-09-22 23:34 UTC and ended at 2026-09-23 00:32 UTC. It lasted 58 min.

How do I get alerts for Pinecone?

Subscribe to the Pinecone live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Pinecone. outages.live reads it every few minutes and keeps every update.

PineconeIncident · 2026-09-22 23:34 UTC

[Serverless][AWS][eu-west-1] 5xx on read requests

ResolvedOfficial update

This incident has been resolved.

The latest update from Pinecone.

State

Resolved

Started

39 d ago

2026-09-22 23:34 UTC

Lasted

58 min

until 2026-09-23 00:32 UTC

Worst impact

Partial outage

Timeline

3 updates

23:3423:4900:0300:1800:32

Partial outageUpdate postedTimes in UTC

Identified

31 min 54%

Monitoring

27 min 46%

Updates

Times in UTC

As posted by Pinecone

Resolved2026-09-23 00:32 UTC

This incident has been resolved.

Monitoring2026-09-23 00:05 UTC

We have mitigated the errors and are monitoring to ensure there is no reoccurrence.

Identified2026-09-22 23:34 UTC

The issue has been identified and mitigation is being actioned. A small percentage of read requests are impacted.

Affected components

AWS eu-west-1Serverless Indexes - AWS eu-west-1

Pinecone in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

58 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

11 h 7 min

median 58 min

90 days agoToday

Other Pinecone incidents

All incidents

Pinecone·[Inference] 5xx errors on some `llama-text-embed-v2` requests

Incident is resolved.

Resolvedresolved 18 d ago

Pinecone·[SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize

This incident has been resolved.

Resolvedresolved 25 d ago

Pinecone·[Pods][AWS][us-east-1] Write failures and high latency

The third party dependency recovered, this incident has resolved.

Resolvedresolved 34 d ago

Pinecone·[Serverless][AWS][us-west-2] 5xx errors on the readpath

This incident has been resolved.

Resolvedresolved 45 d ago

Pinecone·5xx errors on some control plane operations

This incident has been resolved.

Resolvedresolved 61 d ago

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.

Prompt

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.cc/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.

RSS

https://outages.cc/feed.xml?providers=pinecone

Slack

/feed subscribe https://outages.cc/feed.xml?providers=pinecone

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane