Understand Rate Limits

Ingestion checks rate limits by endpoint, project, organization, and source IP. Endpoint limits protect a single intake URL, project limits protect a product or environment, organization limits protect the whole workspace, and source IP protection helps reduce abusive bursts from one sender.

When a limit is exceeded, the API returns HTTP 429 with a clear error and does not silently drop the request. Senders should back off and retry later with an idempotency key so duplicate side effects are easier to avoid.

Rate limits protect worker capacity and prevent abuse. Increase plan limits when sustained production traffic exceeds your current plan, or split unrelated traffic across separate endpoints and projects so operations remain easier to inspect.