Loading status…
Pinecone status · AI & APIs · checked (1s 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.
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.
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.
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.
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.
14 other services isuptime tracks were also reporting a problem as of the same check, 1s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Pinecone's status endpoint.
Pinecone has published 38 incidents in the last 12 months, the 20 most recent shown here. Only what Pinecone posted itself — not every problem users hit.
resolved · Sep 17, 05:37 AM (3d ago)
resolved · Sep 1, 03:04 PM (18d ago)
resolved · Aug 25, 03:50 PM (25d ago)
resolved · Jul 21, 07:10 PM (60d ago)
resolved · Jul 20, 04:44 PM (61d ago)
resolved · Jul 12, 11:21 PM (69d ago)
resolved · Jul 9, 09:50 AM (72d ago)
resolved · Jun 18, 10:00 AM (93d ago)
resolved · Jun 16, 01:05 PM (95d ago)
resolved · Jun 6, 05:05 PM (105d ago)
resolved · Jun 6, 01:05 PM (105d ago)
resolved · Jun 6, 12:48 AM (106d ago)
resolved · May 25, 01:41 PM (117d ago)
resolved · May 13, 08:14 PM (129d ago)
resolved · May 6, 08:02 PM (136d ago)
resolved · May 6, 03:00 PM (136d ago)
resolved · Mar 13, 08:50 AM (190d ago)
resolved · Mar 5, 09:57 PM (198d ago)
resolved · Mar 4, 09:06 PM (199d ago)
resolved · Feb 23, 11:14 PM (208d ago)
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.
