Skip to main content

Why am I getting "429 Too Many Requests" responses from Sentry?

Issue

I see in my application's network logs that POST requests to sentry.io return a 429 Too Many Requests response from Sentry.

Applies To

  • SaaS Sentry users

  • All plans

Resolution

A 429 response is expected and intended. Sentry returns a 429 status code when it drops events server-side, in these cases:

You can see how many events were dropped for these reasons on your Stats page, under the "Rate limited events" category.

To prevent future quota issues, see the Quota Management Guide.

To keep accepting events before the end of the current billing cycle, increase your quota or your Pay-as-you-go (PAYG) budget.

Did this answer your question?