Foxy experienced a minor incident on November 25, 2025 affecting Foxy API, lasting 1h 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 25, 2025, 03:45 PM UTC
We're looking into the cause of a webhooks issue. We'll update as we're able with more info. At this point, webhooks may not be sending as expected.
- monitoring Nov 25, 2025, 05:30 PM UTC
We have identified the cause of the issue, and systems are recovering. Webhooks are being processed currently. No data was lost, but most webhooks were delayed for the past few hours, and will be coming through now. We'll post another update with additional details when everything's fully recovered.
- resolved Nov 25, 2025, 05:37 PM UTC
All webhooks have processed successfully at this point. No data was lost, but webhooks were delayed for many hours while this issue persisted. The root cause is the result of a high-volume Foxy account that had a failing webhook endpoint. Normally this wouldn't cause issues, but a recent change we made to (attempt to) improve the automatic webhook deactivation functionality resulted in unexpected behaviour. As a result, the webhook queue was backed up with failing webhooks. We actually have taken steps to mitigate this possibility in the past, but clearly we still have a bit of work to do to improve the resiliency of the webhook system. We are currently working on an improvement to prevent this from happening in the future. We're terribly sorry for the trouble.