Rate limits

A rate limit caps how many calls per minute a project will accept, so one busy project can't starve the rest. Your limit depends on your plan — see the pricing page for the current numbers.

Two limits, one per pool

• Live traffic (er_live_…) gets your plan's steady limit.
• Test traffic (er_test_…) gets a smaller limit — it's for development, not load.

What 429 means

When you exceed the limit you get a 429 Too Many Requests with a Retry-After header (seconds to wait). Well-behaved senders honour Retry-After and retry — most HTTP clients can do this automatically.

To smooth things out:

• Spread bursts over time rather than firing everything at once.
• Add a small retry-with-backoff in your sender for the occasional 429.

Raising your limit

If you regularly hit the limit, you have options in Billing:

• Move to a higher plan — each plan has a higher steady limit.
• Add rate capacity to a specific project (an add-on), if you only need more on one project rather than across the account.

Changes take effect right away.

Occasional spikes

Short spikes above your steady limit may be absorbed automatically on eligible plans — you don't need to do anything. Sustained load is what needs a higher plan or add-on.

For the exact enforcement rules, see the API reference.