Pinecone reported "5xx errors on some control plane operations" on its status page at 2026-09-01 15:04 UTC.

Pinecone lists these components: Console, Index Management, Assistant.

When did the incident start and end?

It started at 2026-09-01 15:04 UTC and ended at 2026-09-01 19:40 UTC. It lasted 4 h 36 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-01 15:04 UTC

5xx errors on some control plane operations

ResolvedOfficial update

This incident has been resolved.

The latest update from Pinecone.

State

Resolved

Started

61 d ago

2026-09-01 15:04 UTC

Lasted

4 h 36 min

until 2026-09-01 19:40 UTC

Worst impact

Partial outage

Timeline

4 updates

15:0416:1317:2218:3119:40

Partial outageUpdate postedTimes in UTC

Investigating

1 h 56 min 42%

Monitoring

2 h 40 min 58%

Updates

Times in UTC

As posted by Pinecone

Resolved2026-09-01 19:40 UTC

This incident has been resolved.

Monitoring2026-09-01 17:00 UTC

Error rates have subsided, we are monitoring the results.

Investigating2026-09-01 15:39 UTC

This is likely related to ongoing issues in GCP. Affected services include Console, Index management, Assistant management, and APIs served at api.pinecone.io

Investigating2026-09-01 15:04 UTC

We are currently investigating this issue.

Affected components

ConsoleIndex ManagementAssistant

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

4.8× 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][eu-west-1] 5xx on read requests

This incident has been resolved.

Resolvedresolved 39 d ago

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

This incident has been resolved.

Resolvedresolved 45 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