Webhook Rate Limit Alerts and Diagnostics
High-volume upstream systems can flood your incident workflows with redundant webhooks. All Quiet protects your teams from alert fatigue by dropping excessive payloads and returning an HTTP 429 status code. Now, we keep your admins posted if you run into these rate limits.
Published: Thursday, 03 September 2026
High-volume upstream systems can flood your incident workflows with redundant webhooks. All Quiet protects your teams from alert fatigue by dropping excessive payloads and returning an HTTP 429 status code. Now, we keep your admins posted if you run into these rate limits.
See current webhook payload limits in API and Webhook Rate Limits.
Unchanged
- We continue to drop requests that exceed webhook payload limits.
- Blocked requests return an HTTP 429 status code and do not trigger incidents.
New: Automated Rate Limit Alerts
- We now email Team Administrators, Organization Administrators, and Owners after a webhook integration triggers a 429 error.
- We send follow-up emails every 24 hours until traffic normalizes. We won't send reminders if the traffic normalized after 24 hours.
- A new orange Rate limited badge appears on your integration header during active surges. It clears automatically when the system stops receiving excess requests.
New: Rate Limiting Report Diagnostics
You can access this new diagnostic report via the integration settings, the warning badge, or the alert email to pinpoint the source of the excessive traffic and tune your deduplication settings.
| Metric | Details |
|---|---|
| Time Range | Review data up to 180 days. The default view shows the past 7 days. |
| Request Volume | Track blocked requests in a bar chart grouped by 5 minutes, 15 minutes, hours, or days. Hover over any bar to view specific counts. |
| Source IPs | Identify the exact IP addresses generating the excess traffic and view their blocked request counts. |
Published