IXON incident

Report scheduling disabled

Minor Resolved View vendor source →

IXON experienced a minor incident on May 21, 2026 affecting Email delivery and Email delivery (Email delivery), lasting 17m. The incident has been resolved; the full update timeline is below.

Started
May 21, 2026, 07:23 AM UTC
Resolved
May 21, 2026, 07:41 AM UTC
Duration
17m
Detected by Pingoru
May 21, 2026, 07:23 AM UTC

Affected components

Email deliveryEmail delivery (Email delivery)

Update timeline

  1. identified May 21, 2026, 07:23 AM UTC

    There is an issue with scheduling reports where too many reports are being send out. The issue has been identified and a fix is being implemented. Back to current status SUBSCRIBE Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

  2. identified May 21, 2026, 07:23 AM UTC

    There is an issue with scheduling reports where too many reports are being send out. The issue has been identified and a fix is being implemented.

  3. monitoring May 21, 2026, 07:32 AM UTC

    A fix has been implemented and we are monitoring the results. The backlog of incorrectly scheduled reports is removed. May 21, 2026 09:23 CEST

  4. monitoring May 21, 2026, 07:32 AM UTC

    A fix has been implemented and we are monitoring the results. The backlog of incorrectly scheduled reports is removed.

  5. resolved May 21, 2026, 07:41 AM UTC

    The incident has been resolved. May 21, 2026 09:32 CEST