Is IXON down?
Last checked 4m agoNo incidents right now.
IXON is operational right now. Last checked 4m ago; the most recent incident resolved 9d ago.
Real-time IXON status, recent outages, and incident history: pulled directly from IXON's official status page at status.ixon.cloud every 5 minutes. Pingoru tracks 50 IXON services and has captured 11 incidents in the last 90 days (96.47% uptime). Get email, Slack, Discord, or webhook alerts the moment IXON reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- WebAccessWebAccess — NL-AMS - WebAccessWebAccess — SG-SIN - WebAccessWebAccess — US-NYC - WebAccessWebAccess — US-SFO - WebAccessVPN ConnectionVPN Connection — AMER - BR - São PauloVPN Connection — AMER - US - AtlantaVPN Connection — AMER - US - DallasVPN Connection — AMER - US - Newark
Timeline · 9 updates
- 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.
- 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
- 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
- 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.
- 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
- 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.
- monitoring · Oct 21, 2026, 06:57 AM UTC
The fix has been applied to the mentioned servers. October 20, 2026 16:47 CEST
- monitoring · Oct 21, 2026, 06:57 AM UTC
The fix has been applied to the mentioned servers.
- 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
Latest: The rollout during the emergency scheduled maintenance we just completed, fixes what caused this incident. October 21, 2026 08:57 CEST
-
- VPN ConnectionVPN Connection — AMER - BR - São PauloVPN Connection — AMER - US - AtlantaVPN Connection — AMER - US - DallasVPN Connection — AMER - US - NewarkVPN Connection — AMER - US - San FranciscoVPN Connection — AMER - US - SeattleVPN Connection — APAC - AU - MelbourneVPN Connection — APAC - AU - SydneyVPN Connection — APAC - HK - Hong Kong
Timeline · 7 updates
- 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.
- 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
- 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
- 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.
- 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
- 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.
- resolved · Oct 12, 2026, 02:33 PM UTC
We believe this issue to be resolved. October 12, 2026 15:41 CEST
Latest: We believe this issue to be resolved. October 12, 2026 15:41 CEST
-
- PortalPortal — cloud1.ixon.cloudPortal — portal.ixon.cloudAPI ConnectionAPI Connection — APIAPI Connection — Device APIMQTT ConnectionMQTT Connection — Remote Config PushMQTT Connection — Remote Firmware UpgradeCloud Logging
Timeline · 7 updates
- 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
- 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.
- 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
- 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.
- 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
- 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.
- 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
Latest: The platform has stabilized and we see no further degraded performance. We consider this incident resolved. October 7, 2026 11:52 CEST
-
- PortalPortal — portal.ixon.cloud
Timeline · 3 updates
- investigating · Oct 06, 2026, 01:03 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
- investigating · Oct 06, 2026, 01:03 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.
- resolved · Oct 06, 2026, 01:40 PM UTC
The incident has been resolved. October 6, 2026 15:03 CEST
Latest: The incident has been resolved. October 6, 2026 15:03 CEST
-
- Mobile AppMobile App — Android AppMobile App — iOS App
Timeline · 5 updates
- 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
- investigating · Oct 06, 2026, 07:48 AM UTC
We are investigating failing authentication in the Mobile App when using SSO.
- 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
- identified · Oct 06, 2026, 09:02 AM UTC
We have found what is causing this and are working on a fix.
- resolved · Oct 06, 2026, 11:02 AM UTC
This problem has been resolved. October 6, 2026 11:02 CEST
Latest: This problem has been resolved. October 6, 2026 11:02 CEST
-
See the full IXON outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse IXON outage history →Or sign up free to get alerts when IXON breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · Status.io · 50 components checked every 5 minutesThe longest incident in the last year, VNC issues on June 17, 2026, ran for 6 days. 10 maintenance windows announced in the same period.
Most affected components, last 12 months
- Portal6
- Portal — portal.ixon.cloud6
- WebAccess4
- WebAccess — NL-AMS - WebAccess4
- WebAccess — SG-SIN - WebAccess4
Latest incidents
- Intermittent VPN connection issues
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…
- Devices unable to come online
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…
- Platform unreachable
We are currently experiencing issues with the platform. We are assessing the full impact and implementing mitigation measures. Further updates will be provided…
- Intermittent VPN connection issues ResolvedStarted Oct 16, 2026, 11:46 AM UTC · Resolved Oct 22, 2026, 09:24 AM UTC · 5d 21h
- Devices unable to come online ResolvedStarted Oct 12, 2026, 09:41 AM UTC · Resolved Oct 12, 2026, 02:33 PM UTC · 4h 52m
- Platform unreachable ResolvedStarted Oct 07, 2026, 08:15 AM UTC · Resolved Oct 07, 2026, 10:10 AM UTC · 1h 55m
- Platform unreachable ResolvedStarted Oct 06, 2026, 01:03 PM UTC · Resolved Oct 06, 2026, 01:40 PM UTC · 36m
- Started Sep 30, 2026, 01:07 PM UTC · Resolved Oct 06, 2026, 11:02 AM UTC · 5d 21h
- Platform unreachable ResolvedStarted Sep 22, 2026, 12:18 PM UTC · Resolved Sep 22, 2026, 12:59 PM UTC · 40m
- VNC issues ResolvedStarted Sep 09, 2026, 11:52 AM UTC · Resolved Sep 09, 2026, 02:41 PM UTC · 2h 48m