IXON Outage History

Started Oct 16, 2026, 11:46 AM UTC· resolved Oct 22, 2026, 09:24 AM UTC

1. identified Oct 16, 2026, 11:46 AM UTC

   We have identified an issue with broken VPN connections where the device can't be reached. A workaround would be toggling the VPN off and on again We apologize for any inconvenience and will keep you posted.

2. identified Oct 16, 2026, 11:46 AM UTC

   We have identified an issue with broken VPN connections where the device can't be reached. A workaround would be toggling the VPN off and on again We apologize for any inconvenience and will keep you posted. 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

3. identified Oct 20, 2026, 11:08 AM UTC

   We have identified what is causing this issue, that affects a portion of the devices connected to the platform, and are currently testing a fix for this internally. When these tests are successful, we will plan an emergency scheduled maintenance window to deploy the fix to our entire VPN server fleet. October 16, 2026 13:46 CEST

4. identified Oct 20, 2026, 11:08 AM UTC

   We have identified what is causing this issue, that affects a portion of the devices connected to the platform, and are currently testing a fix for this internally. When these tests are successful, we will plan an emergency scheduled maintenance window to deploy the fix to our entire VPN server fleet.

5. monitoring Oct 20, 2026, 02:47 PM UTC

   Our internal tests were successful and we will rollout the fix to a selected number of servers tomorrow 2026-10-21 at 06:30 UTC: - DE Frankfurt #6 - DE Frankfurt #7 - NL Amsterdam #1 - US Newark #1 If the selected public rollout is successful, we will announce a full rollout in the form of an emergency scheduled maintenance. October 20, 2026 13:08 CEST

6. monitoring Oct 20, 2026, 02:47 PM UTC

   Our internal tests were successful and we will rollout the fix to a selected number of servers tomorrow 2026-10-21 at 06:30 UTC: - DE Frankfurt #6 - DE Frankfurt #7 - NL Amsterdam #1 - US Newark #1 If the selected public rollout is successful, we will announce a full rollout in the form of an emergency scheduled maintenance.

7. monitoring Oct 21, 2026, 06:57 AM UTC

   The fix has been applied to the mentioned servers. October 20, 2026 16:47 CEST

8. monitoring Oct 21, 2026, 06:57 AM UTC

   The fix has been applied to the mentioned servers.

9. resolved Oct 22, 2026, 09:24 AM UTC

   The rollout during the emergency scheduled maintenance we just completed, fixes what caused this incident. October 21, 2026 08:57 CEST

Read the full incident report →

Started Oct 12, 2026, 09:41 AM UTC· resolved Oct 12, 2026, 02:33 PM UTC

1. investigating Oct 12, 2026, 09:41 AM UTC

   We are aware of, and are investigating, issues with some devices not coming online and where users are unable to "VPN connect". Initial assessment of the problem shows that this is not related to our maintenance this morning. We are working to understand the full impact. More updates to follow shortly.

2. investigating Oct 12, 2026, 09:41 AM UTC

   We are aware of, and are investigating, issues with some devices not coming online and where users are unable to "VPN connect". Initial assessment of the problem shows that this is not related to our maintenance this morning. We are working to understand the full impact. 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

3. identified Oct 12, 2026, 11:34 AM UTC

   We have identified that this is a DNS related problem. Some resolving DNS providers are unable to reply to specific domain name requests used by our platforms. Of the large public DNS resolvers, we see intermittent issues with the following providers: - Quad9 (i.e. 9.9.9.9) - AdGuard DNS (i.e. 94.140.14.14) - KPN (received through SIM DHCP) We validated that the following public resolvers are responding correctly: - Google Public DNS (i.e. 8.8.8.8) - Cloudflare Public DNS (i.e. 1.1.1.1) - Cisco Umbrella (formerly OpenDNS) (i.e. 208.67.222.222) A workaround for this problem would be to use the working public DNS resolvers. Together with our DNS provider, we are checking what causes this intermittent behavior. October 12, 2026 11:41 CEST

4. identified Oct 12, 2026, 11:34 AM UTC

   We have identified that this is a DNS related problem. Some resolving DNS providers are unable to reply to specific domain name requests used by our platforms. Of the large public DNS resolvers, we see intermittent issues with the following providers: - Quad9 (i.e. 9.9.9.9) - AdGuard DNS (i.e. 94.140.14.14) We validated that the following public resolvers are responding correctly: - Google Public DNS (i.e. 8.8.8.8 & 4.4.4.4) - Cloudflare Public DNS (i.e. 1.1.1.1) - Cisco Umbrella (formerly OpenDNS) (i.e. 208.67.222.222) A workaround for this problem would be to use the working public DNS resolvers. Together with our DNS provider, we are checking what causes this intermittent behavior.

5. monitoring Oct 12, 2026, 01:41 PM UTC

   Together with our DNS provider we have made changes that should start appearing at all caching nameservers worldwide. Due to TTL on the affected records, please give 15 minutes for the changes to be active on your side. October 12, 2026 13:34 CEST

6. monitoring Oct 12, 2026, 01:41 PM UTC

   Together with our DNS provider we have made changes that should start appearing at all caching nameservers worldwide. Due to TTL on the affected records, please give 15 minutes for the changes to be active on your side.

7. resolved Oct 12, 2026, 02:33 PM UTC

   We believe this issue to be resolved. October 12, 2026 15:41 CEST

Read the full incident report →

Started Oct 07, 2026, 08:15 AM UTC· resolved Oct 07, 2026, 10:10 AM UTC

1. investigating Oct 07, 2026, 08:15 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 Oct 07, 2026, 09:19 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. identified Oct 07, 2026, 09:33 AM UTC

   We have identified what is the probable cause of the degraded performance. Our main platform's database reached a threshold that requires immediate capacity scaling. Therefore we have decided to announce an emergency maintenance window, starting immediately. During this emergency maintenance window, users will experience service disruption. We believe this emergency window to take approximately 15 minutes. We will keep you posted. October 7, 2026 10:15 CEST

4. identified Oct 07, 2026, 09:33 AM UTC

   We have identified what is the probable cause of the degraded performance. Our main platform's database reached a threshold that requires immediate capacity scaling. Therefore we have decided to announce an emergency maintenance window, starting immediately. During this emergency maintenance window, users will experience service disruption. We believe this emergency window to take approximately 15 minutes. We will keep you posted.

5. monitoring Oct 07, 2026, 09:52 AM UTC

   The capacity increase has been successful and the platform is reachable again. We are monitoring the situation. October 7, 2026 11:33 CEST

6. monitoring Oct 07, 2026, 09:52 AM UTC

   The capacity increase has been successful and the platform is reachable again. We are monitoring the situation.

7. resolved Oct 07, 2026, 10:10 AM UTC

   The platform has stabilized and we see no further degraded performance. We consider this incident resolved. October 7, 2026 11:52 CEST

Read the full incident report →

Started Sep 30, 2026, 01:07 PM UTC· resolved Oct 06, 2026, 11:02 AM UTC

1. investigating Sep 30, 2026, 01:07 PM UTC

   We are investigating failing authentication in the Mobile App when using SSO. 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 Oct 06, 2026, 07:48 AM UTC

   We are investigating failing authentication in the Mobile App when using SSO.

3. identified Oct 06, 2026, 09:02 AM UTC

   We have found what is causing this and are working on a fix. September 30, 2026 15:07 CEST

4. identified Oct 06, 2026, 09:02 AM UTC

   We have found what is causing this and are working on a fix.

5. resolved Oct 06, 2026, 11:02 AM UTC

   This problem has been resolved. October 6, 2026 11:02 CEST

Read the full incident report →

Started Sep 09, 2026, 11:52 AM UTC· resolved Sep 09, 2026, 02:41 PM UTC

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 →

Started Jul 29, 2026, 12:27 PM UTC· resolved Jul 29, 2026, 01:25 PM UTC

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 →

Started Jun 24, 2026, 02:27 PM UTC· resolved Jun 24, 2026, 06:15 PM UTC

1. investigating Jun 24, 2026, 02:27 PM UTC

   We are aware of, and are investigating, issues with our mail provider. We are working to understand the full impact and mitigate this problem. While we are investigating this issue e-mails from the platform could be delayed. 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 24, 2026, 02:27 PM UTC

   We are aware of, and are investigating, issues with our mail provider. We are working to understand the full impact and mitigate this problem. While we are investigating this issue e-mails from the platform could be delayed. More updates to follow shortly.

3. resolved Jun 24, 2026, 06:15 PM UTC

   The incident has been resolved. June 24, 2026 16:27 CEST

Read the full incident report →

Started Jun 23, 2026, 06:54 AM UTC· resolved Jun 23, 2026, 10:11 AM UTC

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 →

Started Jun 08, 2026, 12:46 PM UTC· resolved Jun 08, 2026, 02:24 PM UTC

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 →

Started May 21, 2026, 07:23 AM UTC· resolved May 21, 2026, 07:41 AM UTC

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 →