TimescaleDB / Tiger Data · Rate Limits

Timescaledb Rate Limits

Tiger Cloud's REST API governs control-plane operations (provisioning, scaling). Public docs do not enumerate explicit per-second rate ceilings; standard HTTP status codes including 429 are documented in the OpenAPI. Database-level resource limits (max connections, IOPS, bandwidth) are enforced per service tier, not as REST rate limits.

Timescaledb Rate Limits is the machine-readable rate-limit profile for TimescaleDB / Tiger Data on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and iops.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Database, Time-Series, PostgreSQL, Open Source, and Cloud.

4 Limits Throttle: 429
DatabaseTime-SeriesPostgreSQLOpen SourceCloudRate LimitingQuotasThrottling

Limits

Tiger Cloud REST control-plane api_key
requests · window
see Tiger Cloud documentation
Limits are enforced for control-plane operations; specific numbers not publicly documented.
Performance tier — max IOPS service
iops
5000
Performance plan; 250 Mbps bandwidth.
Scale tier — max IOPS service
iops
40000
Scale plan; 1,000 Mbps bandwidth.
Enterprise tier — max IOPS service
iops
80000
Enterprise plan; 4,000 Mbps bandwidth.

Policies

Backoff Strategy
Honor Retry-After on 429 responses; use exponential backoff with jitter.
Connection Pooling
Use Tiger's pooled endpoint or external poolers (PgBouncer) to stay under PostgreSQL max-connections.

Sources