Hypernode incident
Degraded performance when applying changes to Hypernodes
Resolved after 57 minutes, affecting Hypernode Toolset / API / Control Panel, on July 9, 2026.
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.
Affected components
Update timeline
- 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.
- 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.
- 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.
- resolved Jul 09, 2026, 10:37 AM UTC
This incident has been resolved.
Your product runs on more than Hypernode
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