Where does this status come from?

From Pinecone's own status page API at https://status.pinecone.io. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Pinecone's words.

How can my agent or app check Pinecone status?

Fetch https://upbutler.com/status/pinecone/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"pinecone"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Pinecone's?

Add "pinecone" to the dependencies of your UpButler workspace. When one of your monitors fails while Pinecone has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Pinecone down?

Right now

No. Pinecone is operational.

No incidents reported.

Read from status.pinecone.io 56 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/pinecone/status.agent.json

MCP: upstream_status {"service":"pinecone"}

Managed vector database. Regional incidents are common: check the component for your index region.

What Pinecone reports

Operational

Taken as is from Pinecone's own status page API. Incident titles and component names below are theirs.

Open status.pinecone.io

UpButler's independent probe

There is no keyless endpoint of Pinecone that says anything useful, so UpButler does not probe it. To check your own Pinecone account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Pinecone components

26 operational

Pod Indexes

us-west1-gcpOperational
us-east1-gcpOperational
us-central1-gcpOperational
us-west4-gcpOperational
us-east4-gcpOperational
us-west1-gcp-freeOperational
us-west4-gcp-freeOperational
gcp-starterOperational
eu-west1-gcpOperational
eu-west4-gcpOperational
asia-southeast1-gcpOperational
asia-northeast1-gcpOperational
asia-southeast1-gcp-freeOperational
northamerica-northeast1-gcpOperational
eastus-azureOperational
us-east-1-awsOperational

ConsoleOperational
Index ManagementOperational
InferenceOperational
AssistantOperational

Serverless Indexes

AWS us-west-2Operational
AWS us-east-1Operational
AWS eu-west-1Operational
Azure eastus2Operational
GCP us-central1Operational
GCP europe-west4Operational

Pinecone incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Pinecone.

Started (UTC)	Incident	Impact	Lasted
2026-10-07 20:40	[SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize	major	1 h 10 min
2026-09-28 04:13	[Pods][AWS][us-east-1] Write failures and high latency	minor	8 min

Tell your outage from Pinecone's

Declare that your project depends on Pinecone. When one of your monitors fails while Pinecone has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - pinecone

Ask before you retry

curl -s https://upbutler.com/status/pinecone/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "pinecone",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Pinecone down right now?: No. As of 2026-10-10 05:10 UTC, Pinecone is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Pinecone's own status page API at https://status.pinecone.io. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Pinecone's words.
How can my agent or app check Pinecone status?: Fetch https://upbutler.com/status/pinecone/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"pinecone"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Pinecone's?: Add "pinecone" to the dependencies of your UpButler workspace. When one of your monitors fails while Pinecone has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in databases and data

UpButler is not affiliated with Pinecone. Status and incident text belong to Pinecone and are read from their public status source; the probe result is UpButler's own measurement.