IXON Outage History

IXON is up right now

IXON had 3 outages in the last 2 years totaling 4h 56m of downtime — averaging 0.1 incidents per month.

There were 3 IXON outages since May 12, 2026 totaling 4h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ixon.cloud

Minor June 8, 2026

Issues with VNC EasyControl

Detected by Pingoru
Jun 08, 2026, 12:46 PM UTC
Resolved
Jun 08, 2026, 02:24 PM UTC
Duration
1h 37m
Affected: WebAccessWebAccess (NL-AMS - WebAccess)WebAccess (SG-SIN - WebAccess)WebAccess (US-NYC - WebAccess)WebAccess (US-SFO - WebAccess)
Timeline · 5 updates
  1. investigating Jun 08, 2026, 12:46 PM UTC

    Users attempting to use VNC EasyControl may experience failures. We are investigating the problem. 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 08, 2026, 12:46 PM UTC

    Users attempting to use VNC EasyControl may experience failures. We are investigating the problem.

  3. monitoring Jun 08, 2026, 01:08 PM UTC

    We have identified what was causing the disruption and have mitigated the problem. We are monitoring the situation. June 8, 2026 14:46 CEST

  4. monitoring Jun 08, 2026, 01:08 PM UTC

    We have identified what was causing the disruption and have mitigated the problem. We are monitoring the situation.

  5. resolved Jun 08, 2026, 02:24 PM UTC

    The incident has been resolved. June 8, 2026 15:08 CEST

Read the full incident report →

Minor June 4, 2026

Platform unreachable

Detected by Pingoru
Jun 04, 2026, 09:30 AM UTC
Resolved
Jun 04, 2026, 12:32 PM UTC
Duration
3h 2m
Affected: PortalPortal (portal.ixon.cloud)API ConnectionAPI Connection (API)API Connection (Device API)
Timeline · 5 updates
  1. investigating Jun 04, 2026, 09:30 AM UTC

    We are currently experiencing issues with the platform. We are assessing the full impact and implementing mitigation measures. Further updates will be provided 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 04, 2026, 10:52 AM UTC

    We are currently experiencing issues with the platform. We are assessing the full impact and implementing mitigation measures. Further updates will be provided shortly.

  3. monitoring Jun 04, 2026, 11:06 AM UTC

    A fix has been implemented and we are monitoring the results. Most of the platform seems to run properly. The exception is the processing of incoming logging data. No data is lost, but it can take up to an hour before data is visible in your dashboards. June 4, 2026 11:30 CEST

  4. monitoring Jun 04, 2026, 11:06 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jun 04, 2026, 12:32 PM UTC

    The incident has been resolved. Just after we started the maintenance, our provider had an incident with their control pane. This greatly extended the impact of the downtime. June 4, 2026 13:06 CEST

Read the full incident report →

Minor May 21, 2026

Report scheduling disabled

Detected by Pingoru
May 21, 2026, 07:23 AM UTC
Resolved
May 21, 2026, 07:41 AM UTC
Duration
17m
Affected: Email deliveryEmail delivery (Email delivery)
Timeline · 5 updates
  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

Read the full incident report →