Tigris Data Rate Limits
Tigris is S3-compatible and applies request throttling consistent with the S3 protocol rather than fixed per-minute quotas. When a client exceeds the rate the service can sustain for a given key prefix it returns HTTP 503 SlowDown (and 429 for some control-plane operations); clients should retry with exponential backoff and jitter, which the AWS SDKs do automatically. Tigris scales request capacity automatically as traffic ramps and recommends spreading high-throughput workloads across key prefixes. Specific numeric per-account limits are not publicly documented and are not reconciled here.
Tigris Data Rate Limits is the machine-readable rate-limit profile for Tigris on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and bytes.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and throttledAlt.
Tagged areas include Object Storage, S3 Compatible, Storage, Multi-Cloud, and Globally Distributed.
Limits
Policies
Sources
- https://www.tigrisdata.com/docs/
- https://www.tigrisdata.com/docs/api/s3/
- https://www.tigrisdata.com/docs/support/
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/tigris-data-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.