Incident with Webhooks

Update timeline

1. investigating Mar 09, 2026, 03:50 PM UTC

   We are investigating reports of degraded performance for Webhooks

2. investigating Mar 09, 2026, 03:56 PM UTC

   We are experiencing latency on the API and UI endpoints. We are working to resolve the issue.

3. investigating Mar 09, 2026, 05:03 PM UTC

   Webhooks is operating normally.

4. resolved Mar 09, 2026, 05:03 PM UTC

   On March 9, 2026, between 15:03 and 20:52 UTC, the Webhooks API experienced was degraded, resulted in higher average latency on requests and in certain cases error responses. Approximately 0.6% of total requests exceeded the normal latency threshold of 3s, while 0.4% of requests resulted in 500 errors. At peak, 2.0% experienced latency greater than 3 seconds and 2.8% of requests returned 500 errors. The issue was caused by a noisy actor that led to resource contention on the Webhooks API service. We mitigated the issue initially by increasing CPU resources for the Webhooks API service, and ultimately applied lower rate limiting thresholds to the noisy actor to prevent further impact to other users. We are working to improve monitoring to more quickly ascertain noisy traffic and will continue to improve our rate-limiting mechanisms to help prevent similar issues in the future.