Resolved after 5 days 21 hours, affecting WebAccess and WebAccess (WebAccess — NL-AMS - WebAccess) and 1 more, on October 16, 2026.
The rollout during the emergency scheduled maintenance we just completed, fixes what caused this incident. October 21, 2026 08:57 CEST
Affected components
Update timeline
- 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
Your product runs on more than IXON
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services