Skip to main content
Error rate spike alerts you when the share of failed requests goes above a percentage you set. Use it as an early warning that something is broken: a misconfigured client, an outage at a provider, or a bad deploy on your end.

When to use it

  • Catching elevated failure rates before users start complaining.
  • Knowing when an integration is silently failing in the background.
  • Tracking provider-side issues without watching dashboards.
This alert needs enough traffic for the percentage to be meaningful. Very low-volume accounts may not see it fire often.

What you configure

Organization scope is available if your role can see organization-level traffic.

Narrowing to specific status codes

By default every non-2xx response counts as a failure. Pick one or more status codes to watch only those. The rate is still measured against all of your traffic, so a threshold of 10% with 429 selected means “alert me when more than 10% of my requests are rate limited.” Common combinations: Available codes: 400, 401, 402, 403, 422, 424, 429, 500, 503, 504. These are the codes the API returns for authenticated requests; anything else is never attributed to your account.

How you’re notified

Email and/or SMS, based on your preferences in Settings → Notifications. See the alerts overview for delivery details and cooldown behavior.
Last modified on September 10, 2026