IXON experienced a minor incident on October 12, 2026 affecting VPN Connection and VPN Connection (AMER - BR - São Paulo) and 1 more component, lasting 4h 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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