Tigris · Rate Limits

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.

3 Limits Throttle: 503
Object StorageS3 CompatibleStorageMulti-CloudGlobally DistributedRate LimitingQuotasThrottling

Limits

Request Throttling (SlowDown) account
requests
see provider documentation
S3-style 503 SlowDown when a key prefix is driven beyond sustainable throughput; capacity scales automatically.
Control-Plane Throttling account
requests
see provider documentation
IAM and bucket/account management operations may return 429 under burst; back off and retry.
Object Size object
bytes
use multipart upload for large objects
Use CreateMultipartUpload/UploadPart for large objects; single PutObject is bounded by the S3 single-request object size.

Policies

Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After; the AWS SDKs do this by default.
Prefix Distribution
Spread high-throughput keys across multiple prefixes so request capacity scales across partitions.
Automatic Scaling
Tigris scales request capacity as sustained traffic increases; ramp gradually for very high request rates.

Sources