This page describes usage quotas, rate limits, and hard limits for Pinecone.

Quotas

Quota typeStarter planStandard planEnterprise plan
Projects per organization120100
Pods per organization0300300
Serverless indexes per project52020
Serverless index storage per project2 GBN/AN/A
Namespaces per serverless index10010,00050,000
Pod-based indexes per project0N/AN/A
Pods per project0100100
Collections per project100N/AN/A

Projects per organization

Starter planStandard planEnterprise plan
120100

When you reach this quota for an organization, trying to create projects will fail and return a 403 - QUOTA_EXCEEDED status with the following error:

Request failed. You've reached the max projects allowed in organization <org name>. 
To add more projects, upgrade your plan.

To increase this quota, upgrade your plan or contact support@pinecone.io.

Pods per organization

Starter planStandard planEnterprise plan
0300300

When you reach this quota for an organization, trying to create pod-based indexes in any project in the organization will fail and return a 403 - QUOTA_EXCEEDED status with the following error:

Request failed. You've reached the max projects allowed in organization <org name>. 
To increase this limit, contact support@pinecone.io.

To increase this quota, upgrade your plan or contact support@pinecone.io.

Serverless indexes per project

Starter planStandard planEnterprise plan
52020

When you reach this quota for a project, trying to create serverless indexes in the project will fail and return a 403 - QUOTA_EXCEEDED status with the following error:

Request failed. You've reached the max serverless indexes allowed in project <project>. 
To add more serverless indexes, upgrade your plan.

To increase this quota, upgrade your plan or contact support@pinecone.io.

Serverless index storage per project

This limit applies to organizations on the Starter plan only.
Starter planStandard planEnterprise plan
2 GBN/AN/A

When you’ve reached this quota for a project, updates and upserts into serverless indexes will fail and return a 403 - QUOTA_EXCEEDED status with the following error:

Request failed. You've reached the max storage allowed for project <project name>. 
To update or upsert new data, delete records or upgrade your plan.

To continue writing data into your serverless indexes, delete records to bring you under the limit or upgrade your plan.

Namespaces per serverless index

Starter planStandard planEnterprise plan
10010,00050,000

When you reach this quota for a serverless index, trying to upsert records into a new namespace in the index will fail and return a 403 - QUOTA_EXCEEDED status with the following error:

Request failed. You've reached the max namespaces allowed in serverless index <index name>. To add more namespaces, upgrade your plan.

To increase this quota, upgrade your plan.

These quotas are intended to provide reasonable boundaries and prevent unexpected or unintentional misuse. To increase your quota beyond the standard allotment, contact support.

Pod-based indexes per project

This limit applies to organizations on the Starter plan only.
Starter planStandard planEnterprise plan
0N/AN/A

When you try to create a pod-based index on the Starter plan, the request will fail and return a 403 - QUOTA_EXCEEDED status with the following error:

Request failed. You've reach the max pod-based indexes allowed in project <project name>. 
To add more pod-based indexes, upgrade your plan.

To create pod-based indexes, upgrade your plan.

Pods per project

Starter planStandard planEnterprise plan
0100100

When you reach this quota for a project, trying to create pod-based indexes in the project will fail and return a 403 - QUOTA_EXCEEDED status with the following error:

Request failed. You've reached the max projects allowed in project <project name>. 
To increase this limit, contact support@pinecone.io.

To increase this quota, upgrade your plan or contact support@pinecone.io.

Collections per project

Starter planStandard planEnterprise plan
100N/AN/A

When you reach this quota for a project, trying to create collections in the project will fail and return a 403 - QUOTA_EXCEEDED status with the following error:

Request failed. You've reached the max collections allowed in project <project name>. 
To add more collections, upgrade your plan.

To increase this quota, upgrade your plan.

Rate limits

The following rate limits apply to serverless indexes only.

Limit typeStarter tierStandard tierEnterprise tier
Read units per month per project1,000,000N/AN/A
Write units per month per project2,000,000N/AN/A
Upsert size per second per namespace5000 MB500,000 MB2,500,000 MB
Query read units per second per index100010001000
Update records per second per namespace100100010,000
Fetch requests per second per index100100100
List requests per second per index100100100
Describe index stats requests per second per index100100100

Read units per month per project

This limit applies to organizations on the Starter plan only.
Starter planStandard planEnterprise plan
1,000,000N/AN/A

Read units measure the compute, I/O, and network resources used by fetch, query, and list requests to serverless indexes. When you reach the monthly read unit limit for a project, fetch, query, and list requests to serverless indexes in the project will fail and return a 429 - TOO_MANY_REQUESTS status with the following error:

Request failed. You've reached your read unit limit for the current month limit. 
To continue reading data, upgrade your plan. 

To continue reading from serverless indexes in the project, upgrade your plan.

To check how close you are to the monthly read unit limit for a project, do the following:

  1. Open the Pinecone console.
  2. Select the project.
  3. Select any index in the project.
  4. Look under Starter Usage.

Write units per month per project

This limit applies to organizations on the Starter plan only.
Starter tierStandard tierEnterprise tier
2,000,000N/AN/A

Write units measure the storage and compute resources used by upsert, update, and delete requests to serverless indexes. When you reach the monthly write unit limit for a project, upsert, update, and delete requests to serverless indexes in the project will fail and return a 429 - TOO_MANY_REQUESTS status with the following error:

Request failed. You've reached your write unit limit for the current month. 
To continue writing data, upgrade your plan.

To continue writing data to serverless indexes in the project, upgrade your plan.

To check how close you are to the monthly read unit limit for a project, do the following:

  1. Open the Pinecone console.
  2. Select the project.
  3. Select any index in the project.
  4. Look under Starter Usage.

Upsert size per second per namespace

Starter tierStandard tierEnterprise tier
5000 MB500,000 MB2,500,000 MB

When you reach the per second upsert size for a namespace in an index, additional upserts will fail and return a 429 - TOO_MANY_REQUESTS status with the following error:

Request failed. You've reached the max upsert size limit per second for index <index name>. 
Pace your upserts or upgrade your plan.

To increase this limit, upgrade your plan. Otherwise, you can handle this limit by automatically retrying requests with an exponential backoff.

Query read units per second per index

Starter tierStandard tierEnterprise tier
100010001000

Pinecone measures query usage in read units. When you reach the per second limit for queries across all namespaces in an index, additional queries will fail and return a 429 - TOO_MANY_REQUESTS status with the following error:

Request failed. You've reached the max query read units per second for index <index name>. 
Pace your queries.

To handle this limit, automatically retry requests with an exponential backoff.

To check how many read units a query consumes, check the query response.

Update records per second per namespace

Starter tierStandard tierEnterprise tier
100100010,000

When you reach the per second update limit for a namespace in an index, additional updates will fail and return a 429 - TOO_MANY_REQUESTS status with the following error:

Request failed. You've reached the max update records per second for namespace <namespace name>. 
Pace your update requests or upgrade your plan.

To increase this limit, upgrade your plan. Otherwise, you can handle this limit by automatically retrying requests with an exponential backoff.

Fetch requests per second per index

Starter tierStandard tierEnterprise tier
100100100

When you reach the per second fetch limit across all namespaces in an index, additional fetch requests will fail and return a 429 - TOO_MANY_REQUESTS status with the following error:

Request failed. You've reached the max fetch requests per second for index <index name>.
Pace your fetch requests.

To handle this limit, automatically retry requests with an exponential backoff.

List requests per second per index

Starter tierStandard tierEnterprise tier
100100100

When you reach the per second list limit across all namespaces in an index, additional list requests will fail and return a 429 - TOO_MANY_REQUESTS status with the following error:

Request failed. You've reached the max list requests per second for index <index name>.
Pace your list requests.

To handle this limit, automatically retry requests with an exponential backoff.

Describe index stats requests per second per index

Starter tierStandard tierEnterprise tier
100100100

When you reach the per second describe index stats limit across all namespaces in an index, additional list requests will fail and return a 429 - TOO_MANY_REQUESTS status with the following error:

Request failed. You've reached the max describe_index_stats requests per second for index <index>. 
Pace your describe_index_stats requests.

To handle this limit, automatically retry requests with an exponential backoff.

Hard limits

  • Max upsert size is 2 MB.

    To avoid hitting this limit, upsert records in batches of 100 or fewer over multiple upsert requests.

  • Max metadata size per record is 40 KB.

  • Max length for a record ID is 512 characters.

  • Max dimensionality for dense vectors is 20,000.

  • Dense vectors must contain at least one non-zero value.

  • Sparse vectors can contain no more than 1000 non-zero values.

  • Max dimensionality for sparse vectors is 4.2 billion.

  • Max value for top_k, the number of results to return, is 10,000.

  • Max records per fetch or delete request is 1,000.