IXON incident

Issues with VNC EasyControl

Minor Resolved View vendor source →

IXON experienced a minor incident on June 8, 2026 affecting WebAccess and WebAccess (NL-AMS - WebAccess) and 1 more component, lasting 1h 37m. The incident has been resolved; the full update timeline is below.

Started
Jun 08, 2026, 12:46 PM UTC
Resolved
Jun 08, 2026, 02:24 PM UTC
Duration
1h 37m
Detected by Pingoru
Jun 08, 2026, 12:46 PM UTC

Affected components

WebAccessWebAccess (NL-AMS - WebAccess)WebAccess (SG-SIN - WebAccess)WebAccess (US-NYC - WebAccess)WebAccess (US-SFO - WebAccess)

Update timeline

  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