IXON Outage History

IXON is up right now

IXON had 7 outages in the last 2 years totaling 13h 24m of downtime — averaging 0.3 incidents per month.

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

Source: https://status.ixon.cloud

Minor September 22, 2026

Platform unreachable

Detected by Pingoru
Sep 22, 2026, 12:18 PM UTC
Resolved
Sep 22, 2026, 12:59 PM UTC
Duration
40m
Affected: PortalPortal (portal.ixon.cloud)
Timeline · 5 updates
  1. investigating Sep 22, 2026, 12:18 PM 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 Sep 22, 2026, 12:18 PM 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. investigating Sep 22, 2026, 12:41 PM UTC

    Due to high load on our database we are reverting the API release. September 22, 2026 14:18 CEST

  4. investigating Sep 22, 2026, 12:41 PM UTC

    Due to high load on our database we are reverting the API release.

  5. resolved Sep 22, 2026, 12:59 PM UTC

    The incident has been resolved. September 22, 2026 14:41 CEST

Read the full incident report →

Minor September 9, 2026

VNC issues

Detected by Pingoru
Sep 09, 2026, 11:52 AM UTC
Resolved
Sep 09, 2026, 02:41 PM UTC
Duration
2h 48m
Affected: WebAccessWebAccess (NL-AMS - WebAccess)WebAccess (SG-SIN - WebAccess)WebAccess (US-NYC - WebAccess)WebAccess (US-SFO - WebAccess)
Timeline · 5 updates
  1. investigating Sep 09, 2026, 11:52 AM UTC

    We are currently seeing problems with VNC sessions in our WebAccess (EasyControl) offering. Some sessions open as expected while some receive a 519 error. We are investigating what is causing this. 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 Sep 09, 2026, 11:52 AM UTC

    We are currently seeing problems with VNC sessions in our WebAccess (EasyControl) offering. Some sessions open as expected while some receive a 519 error. We are investigating what is causing this.

  3. monitoring Sep 09, 2026, 01:28 PM UTC

    We have implemented a fix and are actively monitoring the situation. September 9, 2026 13:52 CEST

  4. monitoring Sep 09, 2026, 01:28 PM UTC

    We have implemented a fix and are actively monitoring the situation.

  5. resolved Sep 09, 2026, 02:41 PM UTC

    The incident has been resolved. September 9, 2026 15:28 CEST

Read the full incident report →

Minor July 29, 2026

Issues with Remote Config Push

Detected by Pingoru
Jul 29, 2026, 12:27 PM UTC
Resolved
Jul 29, 2026, 01:25 PM UTC
Duration
57m
Affected: MQTT ConnectionMQTT Connection (Remote Config Push)
Timeline · 3 updates
  1. investigating Jul 29, 2026, 12:27 PM UTC

    We are currently investigating issues with remote config push. Your device configuration may not sync to the platform. 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 Jul 29, 2026, 12:27 PM UTC

    We are currently investigating issues with remote config push. Your device configuration may not sync to the platform.

  3. resolved Jul 29, 2026, 01:25 PM UTC

    We have found the root cause and resolved the issue. July 29, 2026 14:27 CEST

Read the full incident report →

Minor June 23, 2026

Partial disruption

Detected by Pingoru
Jun 23, 2026, 06:54 AM UTC
Resolved
Jun 23, 2026, 10:11 AM UTC
Duration
3h 16m
Affected: PortalPortal (portal.ixon.cloud)Cloud NotifyCloud Notify (Notification Processing)Cloud Notify (Notification Center)Cloud Notify (Sending Notifications)Email deliveryEmail delivery (Email delivery)
Timeline · 5 updates
  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

Read the full incident report →

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 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 →