Is Pinecone down?
Pinecone status · AI & APIs · checked (3s ago)
No — Pinecone is not down. All Pinecone systems are reported operational.
According to Pinecone's official status page, Pinecone was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Pinecone's feed reported no outage in 100.00% of our checks.
Is Pinecone down for you right now?
Everything above is read from Pinecone's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Pinecone in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Pinecone is
Pinecone is a managed vector database — the store behind semantic search and retrieval-augmented generation. Applications write embeddings to an index and query it for nearest neighbours, usually on the hot path of a user-facing request.
What Pinecone's status feed covers
Pinecone's status page reports by cloud region, and that is the detail that matters: indexes are pinned to one region, so an incident in us-east-1 says nothing about an index in eu-west-1. Control-plane operations (creating and configuring indexes) are reported separately from the data plane that serves queries, and the control plane fails more often.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
Pinecone uptime, last 30 days
One bar per day. Each shows the share of that day's checks where Pinecone's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Pinecone was down.
- No outage reported (99%+)
- 95–99%
- 80–95%
- Under 80%
- No data
Other services reporting problems right now
10 other services isuptime tracks were also reporting a problem as of the same check, 3s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
CloudflarePartial System Outage
- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
GrafanaMinor Service Outage
- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
Pinecone response time trend
Each point is one check of Pinecone's status endpoint.
Pinecone outage history
Pinecone has published 39 incidents in the last 12 months, the 20 most recent shown here. Only what Pinecone posted itself — not every problem users hit.
- [Metrics Endpoint] 5xx Errors on */metrics/discovery
resolved · Nov 3, 12:30 PM (18h ago)
- [Pod-Based Indexes] Stalled control plane operations.
resolved · Nov 2, 09:00 PM (1d ago)
- [Inference] 5xx errors on some `llama-text-embed-v2` requests
resolved · Oct 14, 02:48 PM (20d ago)
- [SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize
resolved · Oct 7, 08:40 PM (27d ago)
- [Pods][AWS][us-east-1] Write failures and high latency
resolved · Sep 28, 04:07 AM (37d ago)
- [Serverless][AWS][eu-west-1] 5xx on read requests
resolved · Sep 22, 11:34 PM (42d ago)
- [Serverless][AWS][us-west-2] 5xx errors on the readpath
resolved · Sep 17, 05:37 AM (48d ago)
- 5xx errors on some control plane operations
resolved · Sep 1, 03:04 PM (63d ago)
- [SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests
resolved · Aug 25, 03:50 PM (70d ago)
- [SERVERLESS][Azure][eastus2] 5xx errors for some namespaces
resolved · Jul 21, 07:10 PM (105d ago)
- [SERVERLESS][AWS][us-east-1] Increased latency and 5xx errors for some indexes
resolved · Jul 20, 04:44 PM (106d ago)
- [Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces
resolved · Jul 12, 11:21 PM (114d ago)
- [Serverless][Azure][eastus2] 5xx errors on some requests for some indexes
resolved · Jul 9, 09:50 AM (117d ago)
- Some initial queries to infrequently read namespaces incorrectly returning empty results
resolved · Jun 18, 10:00 AM (138d ago)
- [Serverless][AWS][us-east-1] Metrics tab in the console not showing graphs
resolved · Jun 16, 01:05 PM (140d ago)
- [Serverless][AWS][us-west-2] 5xx errors for some requests on some indexes
resolved · Jun 6, 05:05 PM (150d ago)
- [Serverless][AWS][us-west-2] Read path operations for some indexes may experience elevated latency and timeouts
resolved · Jun 6, 01:05 PM (150d ago)
- [AWS][us-east-1] 5xx errors for some requests on some indexes
resolved · Jun 6, 12:48 AM (151d ago)
- [Serverless][AWS][us-west-2] 5xx errors and longer response times on upsert requests for some indexes.
resolved · May 25, 01:41 PM (162d ago)
- [AWS][us-east-1] 5xx errors on read and write operations for some indexes
resolved · May 13, 08:14 PM (174d ago)
Pinecone status — frequently asked
- Is Pinecone down right now?
- No — Pinecone is not down. All Pinecone systems are reported operational. Checked (3s ago).
- What is Pinecone's status right now?
- Pinecone is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 496 ms. isuptime reads this from Pinecone's own published feed and does not test Pinecone independently.
- When did Pinecone last go down?
- The most recent incident Pinecone published was “[Metrics Endpoint] 5xx Errors on */metrics/discovery”, opened Nov 3, 12:30 PM UTC (18h ago) and marked resolved Nov 3, 02:03 PM UTC. That is the latest entry in Pinecone's own incident feed, not every problem users experienced.
- What is Pinecone's uptime?
- isuptime does not measure Pinecone's uptime directly — it reads Pinecone's own published status feed. Over the last 30 days, Pinecone's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
- Is it just me, or is Pinecone down for everyone?
- Pinecone reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
Pinecone says operational but it is not working for me
A query returning no matches is usually a namespace or metadata filter, not an outage — Pinecone will happily return an empty result set for a namespace that does not exist. Newly written vectors are not immediately queryable; that eventual consistency window catches people constantly. Serverless indexes also cold-start after idle periods, adding latency that no incident explains.