Is Pinecone Down?

No — Pinecone is up

Pinecone's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 323 ms

Right now

The verdict is the worse of these two. How we decide

Pinecone's status page

status.pinecone.io · read 2 minutes ago · checked every 3 minutes

Operational

Pinecone's components, as its status page reports them
Component	Status
Console	Operational
Index Management	Operational
Inference	Operational
Assistant	Operational
Azure eastus2	Operational
gcp-starter	Operational
eastus-azure	Operational

19 locations All operational

Open their status page

FlareWarden checks

pinecone.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 323 ms
Checked: 4 hours ago

By region

Ashburn reachable, 181 ms
Chicago reachable, 280 ms
Johannesburg reachable, 629 ms
London reachable, 292 ms
Los Angeles reachable, 165 ms
San Jose reachable, 69 ms
Singapore reachable, 636 ms
Tokyo reachable, 333 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	78 ms	1 ms	6 ms	163 ms
Chicago	118 ms	1 ms	21 ms	267 ms
Johannesburg	238 ms	1 ms	45 ms	606 ms
London	64 ms	2 ms	8 ms	281 ms
Los Angeles	57 ms	1 ms	27 ms	149 ms
San Jose	18 ms	1 ms	10 ms	61 ms
Singapore	284 ms	1 ms	8 ms	630 ms
Tokyo	37 ms	2 ms	9 ms	318 ms

We check that pinecone.io loads, not every feature behind it. Test it yourself

History

Incidents Pinecone reported

Since Oct 22, 2 days · from status.pinecone.io

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Pinecone website availability

Measured by FlareWarden · pinecone.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 395ms

Last 30 days

62-day clean streak

Sep 24 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of pinecone.io from multiple regions every 6 hours. Pinecone's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 62 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Pinecone itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Pinecone goes down

We check Pinecone every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required