InfluxDB Cloud Serverless limits and adjustable quotas

InfluxDB Cloud Serverless applies (non-adjustable) global system limits and adjustable service quotas on a per organization basis.

All rates (data-in (writes), and queries (reads)) are accrued within a fixed five-minute window. Once a rate is exceeded, an error response is returned until the current five-minute window resets.

Review adjustable service quotas and global limits to plan for your bandwidth needs:

Adjustable service quotas

To reduce the chance of unexpected charges and protect the service for all users, InfluxDB Cloud Serverless has adjustable service quotas applied per account.

To request higher service quotas, reach out to InfluxData Support.

Free Plan

  • Data-in: Rate of 5 MB per 5 minutes (average of 17 kb/s)
  • Read: Rate of 300 MB per 5 minutes (average of 1000 kb/s)
    • Bytes in HTTP in response payload
  • Available resources:
    • 2 buckets (excluding _monitoring and _tasks buckets)
  • Storage: 30 days of data retention (see retention period)

To write historical data older than 30 days, retain data for more than 30 days, increase rate limits, or create additional organizations, upgrade to the Cloud Usage-Based Plan.

Usage-Based Plan

Global limits

InfluxDB Cloud Serverless applies global (non-adjustable) system limits to all accounts, which protects the InfluxDB Cloud Serverless infrastructure for all users. As the service continues to evolve, we’ll continue to review these global limits and adjust them as appropriate.

Limits include:

  • Write request limits:
    • 50 MB maximum HTTP request batch size (compressed or uncompressed–defined in the Content-Encoding header)
    • 250 MB maximum HTTP request batch size after decompression
  • Query processing time: 90 seconds
  • Total query time: 1500 seconds of total query time every 30 seconds
  • Task processing time: 150 seconds
  • Total task time: 1500 seconds of total task time every 30 seconds

UI error messages

The InfluxDB Cloud Serverless UI displays a notification message when service quotas or limits are exceeded. The error messages correspond with the relevant API error responses.

Errors can also be viewed in the Usage page under Limit Events, e.g. event_type_limited_query, event_type_limited_write, or event_type_limited_delete_rate.

API error responses

The following API error responses occur when your plan’s service quotas are exceeded.

HTTP response codeError messageDescription
HTTP 413 "Request Too Large"cannot read data: points in batch is too largeIf a write request exceeds the maximum global limit
HTTP 429 "Too Many Requests"Retry-After: xxx (seconds to wait before retrying the request)If a read or write request exceeds your plan’s adjustable service quotas or if a delete request exceeds the maximum global limit

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB 3.0

The new core of InfluxDB built with Rust and Apache Arrow. Available today in InfluxDB Cloud Dedicated.

Learn more

State of the InfluxDB Cloud Serverless documentation

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.

InfluxDB Cloud Serverless powered by IOx