Vendor record
Pinecone
Checked
Front door check counts and Pinecone’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Pinecone endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.pinecone.io
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Pinecone product, region or your app worked.
How we count front door checksPinecone says
Incident posts from Pinecone’s status page, with its titles, impact levels and times. They say what Pinecone chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
16
incidents Pinecone posted, last 1 year
Median recorded duration: 1h 17m. From 16 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
[SERVERLESS][GCP][us-central1] Newly created indexes failing to initialize
MajorPinecone’s postStarted, per Pinecone
Closed in our record(1h 15m)
[Serverless][AWS][eu-west-1] 5xx on read requests
MajorPinecone’s postStarted, per Pinecone
Closed in our record(45m)
[Serverless][AWS][us-west-2] 5xx errors on the readpath
MajorPinecone’s postStarted, per Pinecone
Closed in our record(11h 12m)
5xx errors on some control plane operations
MajorPinecone’s postStarted, per Pinecone
Closed in our record(4h 55m)
5xx errors on some control plane operations
MajorPinecone’s postStarted, per Pinecone
Closed in our record(45m)
11 older records
[SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests
MajorPinecone’s postStarted, per Pinecone
Closed in our record(2h 49m)
[SERVERLESS][Azure][eastus2] 5xx errors for some namespaces
CriticalPinecone’s postStarted, per Pinecone
Closed in our record(1h 17m)
[SERVERLESS][AWS][us-east-1] Increased latency and 5xx errors for some indexes
MinorPinecone’s postStarted, per Pinecone
Closed in our record(45m)
[Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces
MinorPinecone’s postStarted, per Pinecone
Closed in our record(14h 9m)
[Serverless][Azure][eastus2] 5xx errors for some requests on some indexes
MajorPinecone’s postStarted, per Pinecone
Closed in our record(1h 5m)
[Serverless][AWS][us-east-1] Metrics tab in the console not showing graphs
Not specifiedPinecone’s postStarted, per Pinecone
Closed in our record(1h 47m)
[Serverless][AWS][us-west-2] 5xx errors for some requests on some indexes
MajorPinecone’s postStarted, per Pinecone
Closed in our record(5m)
[AWS][us-east-1] 5xx errors for some requests on some indexes
MinorPinecone’s postStarted, per Pinecone
Closed in our record(4h 12m)
[AWS][us-east-1] 5xx errors on read and write operations for some indexes
MajorPinecone’s postStarted, per Pinecone
Closed in our record(15h 11m)
[AWS][us-east-1] 5xx errors for some requests on some indexes
MajorPinecone’s postStarted, per Pinecone
Closed in our record(5m)
Pinecone Console loading slowly for some users
MinorPinecone’s postStarted, per Pinecone
Closed in our record(3h 30m)
Your code, your dependencies
See which of your code paths call Pinecone
Connect GitHub or GitLab to find where your public or private repository uses Pinecone. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Pinecone status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Pinecone currently down?
Pinecone's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Pinecone last have an outage?
The most recent closed incident record began 8 days ago and spans 1h 15m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Pinecone?
No. CheckUpstream checks Pinecone’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Pinecone in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Pinecone?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.