Pusher · Rate Limits

Pusher Rate Limits

Pusher Channels gates per-app concurrent connections and daily message volume by plan tier (100 connections / 200K msg/day on Sandbox up to 30K / 90M on Growth Plus). Server-side HTTP publish endpoints additionally enforce a per-channel-per-second message cap. Beams enforces per-publish payload size and per-instance throughput caps. HTTP 429 is returned when caps are exceeded.

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

It captures 9 rate-limit definitions, measuring concurrent_connections and messages_per_day.

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

Tagged areas include Realtime and Rate Limiting.

9 Limits Throttle: 429
RealtimeRate Limiting

Limits

Sandbox connections app
concurrent_connections
100
Sandbox messages app
messages_per_day
200000
Pro connections app
concurrent_connections
2000
Pro messages app
messages_per_day
4000000
Business connections app
concurrent_connections
5000
Business messages app
messages_per_day
10000000
Growth Plus connections app
concurrent_connections
30000
Growth Plus messages app
messages_per_day
90000000
Enterprise app
concurrent_connections
-1
Sales-led contract.

Policies

Backoff Strategy
Honor 429 Retry-After and apply exponential backoff with jitter.
Per-channel publish
Avoid publishing more than ~10 events/sec to a single channel; shard across channels.

Sources