RudderStack · Rate Limits

Rudderstack Rate Limits

RudderStack does not publish hard request-per-second caps on its HTTP Tracking API; instead, primary metering is monthly events as set by the subscribed plan tier (Free 250K, Starter 1M, Growth/Enterprise custom). The Config Backend API and Dashboard APIs apply lighter throttles primarily to protect the control plane. Self-hosted (open-source) deployments inherit only the limits the operator sets on rudder-server. Downstream destination throughput is bounded by the destination's own rate limits, which RudderStack respects per-connection.

Rudderstack Rate Limits is the machine-readable rate-limit profile for RudderStack on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring events and bytes.

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

Tagged areas include Customer Data Platform, CDP, Event Streaming, Rate Limiting, and Quotas.

6 Limits Throttle: 429
Customer Data PlatformCDPEvent StreamingRate LimitingQuotasThrottling

Limits

Free Plan Monthly Events workspace
events · month
250000
Hard cap on tracked events per month for the Free tier; excess events are dropped or queued depending on settings.
Starter Plan Monthly Events workspace
events · month
1000000
Included events on the $220/month Starter plan; overage is billed or capped per contract.
Growth Plan Monthly Events workspace
events · month
-1
Custom-quoted volume; specific cap is set in the Growth subscription order form.
Enterprise Plan Monthly Events workspace
events · month
-1
Custom-quoted volume with optional burst allowance; defined in the enterprise contract.
HTTP Payload Size request
bytes · per-event
32768
Single tracking call payloads are recommended to stay under 32 KB; batch endpoint accepts up to 4 MB total.
Batch Size request
events · per-batch
500
Typical safe batch size for the /v1/batch endpoint; align with the SDKs' default flush thresholds.

Policies

Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After. The official SDKs already implement queueing, batching, and retry semantics.
Quota Management
Track workspace event volume continuously; alert at 70/85/95% of monthly quota; segment noisy SDKs to a separate workspace if approaching plan limits.
Destination Backpressure
RudderStack enforces destination-specific rate limits per connection. Failing destinations are retried with backoff; persistent failures route to dead-letter storage when configured.

Sources