Questdb Rate Limits
QuestDB does not enforce a managed-service-style request quota. As a self-hosted database, the relevant limits are operational: max concurrent HTTP/PG connections, ILP TCP buffer/queue depth, query timeouts, and per-server CPU/IO budgets. Limits are configurable via server.conf.
Questdb Rate Limits is the machine-readable rate-limit profile for QuestDB on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring workers, connections, and ms.
The profile also includes 2 backoff/retry policies defined and response codes documented for busy.
Tagged areas include Database, Time-Series, SQL, Open Source, and Performance.
Limits
Policies
Sources
- https://questdb.com/docs/operations/capacity-planning/
- https://questdb.com/docs/operations/multiple-databases/
- https://questdb.com/docs/concept/storage-model/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/questdb-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.