Maxio incident

Webhook Delivery Delays

Minor Resolved View vendor source →

Maxio experienced a minor incident on March 10, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 10, 2025, 02:00 PM UTC
Resolved
Mar 10, 2025, 02:00 PM UTC
Duration
Detected by Pingoru
Mar 10, 2025, 02:00 PM UTC

Update timeline

  1. resolved Mar 31, 2025, 06:56 PM UTC

    Incident Dates: Start: 03/10/2025 End: 03/11/2025 Root Cause: A rare communication issue between a background server and an internal service caused disruptions in webhook processing. Impact: Some webhook events were not delivered as expected, potentially leading to delays or inconsistencies for systems relying solely on those notifications. Resolution & Mitigation Steps: The issue was identified and resolved. Monitoring has been improved to catch similar issues earlier. Additional internal safeguards have been put in place to prevent recurrence. Actions Needed: We will contact affected customers to inform them of the issue. Customers will be given the option to have any missing webhook events resent. Best Practices Reminder (link below): Webhooks are asynchronous. We strive for timely delivery, but we DO NOT recommend relying on them for time-sensitive events. Do not block users based on webhook responses. The recommended approach is to verify subscription status using the Subscriptions API. https://developers.maxio.com/http/getting-started/about-the-api/webhooks#best-practices