Hypernode incident

Degraded performance when applying changes to Hypernodes

Minor Resolved View vendor source →

Hypernode experienced a minor incident on July 9, 2026 affecting Hypernode Toolset / API / Control Panel, lasting 57m. The incident has been resolved; the full update timeline is below.

Started
Jul 09, 2026, 09:40 AM UTC
Resolved
Jul 09, 2026, 10:37 AM UTC
Duration
57m
Detected by Pingoru
Jul 09, 2026, 09:40 AM UTC

Affected components

Hypernode Toolset / API / Control Panel

Update timeline

  1. investigating Jul 09, 2026, 09:40 AM UTC

    We're currently experiencing some degradation when making changes to Hypernodes (version changes, whitelists, SSH keys). Please contact support for urgent cases. This does not influence general availability for your server or application.

  2. monitoring Jul 09, 2026, 09:51 AM UTC

    A fix has been rolled out and missed changes will now be handled, please keep an eye out on the `hypernode-log` for any missed actions.

  3. monitoring Jul 09, 2026, 10:36 AM UTC

    All systems operational. A synchronization primitive in our automation system got stuck in a dead state. We're implementing monitoring rules to identify similar issues in the future, while we keep monitoring the system for dead locks.

  4. resolved Jul 09, 2026, 10:37 AM UTC

    This incident has been resolved.