IXON incident

Partial disruption

Minor Resolved View vendor source →

IXON experienced a minor incident on June 23, 2026 affecting Portal and Portal (portal.ixon.cloud) and 1 more component, lasting 3h 16m. The incident has been resolved; the full update timeline is below.

Started
Jun 23, 2026, 06:54 AM UTC
Resolved
Jun 23, 2026, 10:11 AM UTC
Duration
3h 16m
Detected by Pingoru
Jun 23, 2026, 06:54 AM UTC

Affected components

PortalPortal (portal.ixon.cloud)Cloud NotifyCloud Notify (Notification Processing)Cloud Notify (Notification Center)Cloud Notify (Sending Notifications)Email deliveryEmail delivery (Email delivery)

Update timeline

  1. investigating Jun 23, 2026, 06:54 AM UTC

    We are currently seeing issues with our email processing. We are working to understand the full impact and mitigate this problem. More updates to follow shortly. 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. investigating Jun 23, 2026, 06:54 AM UTC

    We are currently seeing issues with our email processing. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

  3. monitoring Jun 23, 2026, 07:32 AM UTC

    We have identified what was causing the disruption and have mitigated the problem. It might be that you receive some old emails that were stuck in our pipeline. June 23, 2026 08:54 CEST

  4. monitoring Jun 23, 2026, 07:32 AM UTC

    We have identified what was causing the disruption and have mitigated the problem. It might be that you receive some old emails that were stuck in our pipeline.

  5. resolved Jun 23, 2026, 10:11 AM UTC

    The incident has been resolved. June 23, 2026 09:32 CEST