Skip to main content

Is Pinecone Down?

No — Pinecone is up

Reachable from all 8 checked regions

Average response time: 419ms

Last checked · checks run every 6 hours

Official status page: https://status.pinecone.io

Pinecone uptime

Last 7 days
Last 30 days
Last 90 days
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: no data
Aug 22: 100.00% uptime, 16 checks
Aug 23: 100.00% uptime, 32 checks
Aug 24: no data
Jul 26 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
383ms
DNS 30ms TCP 3ms TLS 17ms TTFB 371ms
arn
369ms
DNS 163ms TCP 0ms TLS 11ms TTFB 359ms
bom
468ms
DNS 193ms TCP 1ms TLS 8ms TTFB 460ms
cdg
276ms
DNS 19ms TCP 9ms TLS 16ms TTFB 246ms
dfw
344ms
DNS 149ms TCP 4ms TLS 54ms TTFB 317ms
sin
533ms
DNS 194ms TCP 1ms TLS 7ms TTFB 526ms
sjc
244ms
DNS 7ms TCP 1ms TLS 12ms TTFB 238ms
syd
1122ms
DNS 143ms TCP 1ms TLS 9ms TTFB 1115ms
yyz
153ms
DNS 20ms TCP 0ms TLS 20ms TTFB 145ms

What Pinecone does

Pinecone is a managed vector database used to store embeddings and run similarity search, most often behind retrieval-augmented generation features in AI products. Applications write vectors to an index and query it on every user request, so it sits in the hot path of a chatbot or a search feature rather than in a nightly batch job.

What an outage looks like

Queries return errors or hang, and the AI feature built on top answers without its retrieved context or fails outright. Upserts are rejected, so new documents never become searchable. The console may load while indexes are unreachable, or the reverse, because Console and Index Management are tracked apart from the indexes themselves.

What to do about it

Check status.pinecone.io and match the row to your index type and region: Serverless Indexes and Pod Indexes are separate components, each broken out by cloud region such as AWS us-east-1 or GCP europe-west4. Inference and Assistant are listed apart again. Applications that treat retrieval as optional degrade to answering without context, which usually beats failing the whole request.

Is it down for everyone, or just you?

If this page says Pinecone is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Pinecone outage FAQ

Is my data lost if Pinecone goes down?
An availability incident affects reaching the index, not the vectors stored in it, and they are there when the service returns. What is lost is the writes that were rejected during the window, so anything you upserted and did not retry is missing. Pipelines that log failed upserts and replay them afterwards are the ones that recover cleanly.
Does a Pinecone outage affect every region?
Rarely. Pinecone reports serverless indexes per cloud region, currently including AWS us-west-2, us-east-1 and eu-west-1, Azure eastus2, and GCP us-central1 and europe-west4, with pod indexes on a longer list again. An incident usually names specific regions, so find the region your index was created in rather than reading the headline.
Why does my chatbot still answer when Pinecone is down?
Because retrieval failed and the model answered from its own training instead. This is the failure mode worth designing for: the application looks healthy while its answers quietly lose their grounding. Logging retrieval errors separately from request errors is what makes it visible, since neither the user nor an uptime check against the app will show anything wrong.
Are Inference and Assistant affected by an index outage?
Not automatically. Pinecone tracks Inference, which generates embeddings, and Assistant as their own components, separate from the index rows, so embeddings can be produced while the index they belong in is unreachable. If your pipeline embeds and upserts in one step, check both rows before concluding which half failed.

How we measure this

  • We request Pinecone's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Pinecone publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Pinecone goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required