# Pinecone takes about 2-3 minutes for upsert vector to be available for query

**URL:** <https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701>\
**Category:** Support\
**Tags:** vector-database, embeddings\
**Created:** [May 26, 2024, 2:41am UTC](https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701 "2024-05-26T02:41:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vanthanh12195](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/vanthanh12195/32/2645_2.png) [@vanthanh12195](https://community.pinecone.io/u/vanthanh12195)\
**Post date:** [May 26, 2024, 2:41am UTC](https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701/1 "2024-05-26T02:41:48Z")

</div>

Hello everyone,

I’ve noticed that Pinecone takes about 2-3 minutes for an upserted vector to be available for query. My use case involves a user upserting a vector and then querying that vector immediately. A delay of 2-3 seconds would be okay, but 2-3 minutes is problematic for my use case. I am currently using the serverless option with the starter plan.

Has anyone else experienced this delay? Is this the expected behavior, or is there something I might be doing wrong?

Thanks for your help!

---

<div class="post-metadata">

**Author:** ![personaifydev](https://avatars.discourse-cdn.com/v4/letter/p/2bfe46/32.png) [@personaifydev](https://community.pinecone.io/u/personaifydev)\
**Post date:** [May 26, 2024, 2:51am UTC](https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701/2 "2024-05-26T02:51:00Z")

</div>

How many vectors do you have in your index to reach up to 2-3 minute delay? Even with a brand new index, after upserting I have to wait 3-5 seconds before the query shows the data.

This is already very bad from an automation perspective where my tests are then verifying or using the data. I either have to retry or sleep – neither of which is desirable. How are people handling this? This needs to be addressed. After upsert and return from the API, the data needs to be available.

Also see ["There can be a slight delay before new or changed records are visible to queries"](https://community.pinecone.io/t/there-can-be-a-slight-delay-before-new-or-changed-records-are-visible-to-queries/4912)

---

<div class="post-metadata">

**Author:** ![vanthanh12195](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/vanthanh12195/32/2645_2.png) [@vanthanh12195](https://community.pinecone.io/u/vanthanh12195)\
**Post date:** [May 26, 2024, 3:16am UTC](https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701/3 "2024-05-26T03:16:12Z")

</div>

I have about 6,000 vectors, which isn’t a lot. While availability is not always immediate, sometimes it is ready right away, and other times it takes 2-3 minutes before I can query it.

Yesterday, the upsertion was immediate, but today I’m frustrated because it took 2-3 minutes to upsert a batch of 20 vectors (1536 dimensions). I even upgraded to the Standard plan, which costs money, but the upsertion still takes 2-3 minutes.

Another thing I want to point out is: For example if I upsert 1 vector A, after 2-3 mins I did not see that vector available. But If I upsert another vector B, both vector A and B will be available. It is strange.

---

<div class="post-metadata">

**Author:** ![personaifydev](https://avatars.discourse-cdn.com/v4/letter/p/2bfe46/32.png) [@personaifydev](https://community.pinecone.io/u/personaifydev)\
**Post date:** [May 26, 2024, 7:47am UTC](https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701/4 "2024-05-26T07:47:54Z")

</div>

Mandatory migration to serverless should be halted until this issue is addressed. Also see my reply on the other thread.
