Hypernode Outage History

Hypernode is up right now

There were 4 Hypernode outages since February 24, 2026 totaling 52h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.hypernode-status.com

Minor April 14, 2026

Investigating: DNS Resolution Issues Affecting *.hypernode.io

Detected by Pingoru
Apr 14, 2026, 12:18 PM UTC
Resolved
Apr 14, 2026, 01:15 PM UTC
Duration
57m
Affected: Hypernode ServersHypernode Toolset / API / Control Panel
Timeline · 3 updates
  1. identified Apr 14, 2026, 12:18 PM UTC

    We are currently experiencing intermittent downtime affecting services under the *.hypernode.io domain. Our DNS provider is undergoing a large-scale DDoS attack, which is causing instability in domain name resolution. As a result, some requests may fail to resolve or experience delays. We want to emphasize that our platform and infrastructure remain operational; however, access is impacted due to external DNS issues. Our team is actively monitoring the situation and working with the provider to mitigate the impact. We are also exploring mitigation strategies to reduce dependency on the affected service. We will continue to provide updates as more information becomes available.

  2. monitoring Apr 14, 2026, 12:28 PM UTC

    We experienced a brief period of instability affecting DNS resolution for the *.hypernode.io domain, which may have caused temporary downtime or failed requests. Service has since recovered, and all systems are currently operating normally. Initial indications suggested a possible DDoS attack at the DNS provider level; however, this has not been confirmed. We are continuing to monitor the situation closely and are in contact with the provider to better understand the root cause.

  3. resolved Apr 14, 2026, 01:15 PM UTC

    The earlier DNS resolution instability affecting the *.hypernode.io domain has now fully recovered. Stability has been restored and we are no longer observing any degraded performance or resolution failures over an extended period of time.

Read the full incident report →

Major April 13, 2026

Degraded performance on our cloud provider location R405

Detected by Pingoru
Apr 13, 2026, 09:26 AM UTC
Resolved
Apr 13, 2026, 12:53 PM UTC
Duration
3h 26m
Affected: Hypernode Servers
Timeline · 3 updates
  1. identified Apr 13, 2026, 09:26 AM UTC

    Part of our datacenter is currently under a DDoS attack, resulting in degraded performance across multiple nodes. We are actively investigating short-term mitigation options.

  2. monitoring Apr 13, 2026, 09:36 AM UTC

    We have implemented anti-DDoS measures and rebooted the surrounding hypervisors, which has restored normal operations. We will keep monitoring the situation.

  3. resolved Apr 13, 2026, 12:53 PM UTC

    Since implementing these measures and closely monitoring the situation, we have not observed any further downtime or service disruptions.

Read the full incident report →

Major March 24, 2026

Partial service disruption for Brancher, Xgrade, and order processes.

Detected by Pingoru
Mar 24, 2026, 10:45 AM UTC
Resolved
Mar 25, 2026, 12:17 PM UTC
Duration
1d 1h
Affected: Hypernode Toolset / API / Control Panel
Timeline · 4 updates
  1. investigating Mar 24, 2026, 10:45 AM UTC

    We are currently experiencing issues with creating branchers, performing upgrades, and provisioning ordered Hypernodes. Our team is actively working to investigate and resolve the problem.

  2. identified Mar 24, 2026, 03:13 PM UTC

    We have identified the issue and are currently working on a fix.

  3. monitoring Mar 24, 2026, 07:23 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 25, 2026, 12:17 PM UTC

    The issue has been resolved. A fix was successfully implemented, and we are continuing to monitor the results to ensure stability.

Read the full incident report →

Minor February 24, 2026

Control Panel Performance Degradation

Detected by Pingoru
Feb 24, 2026, 09:59 AM UTC
Resolved
Feb 25, 2026, 08:15 AM UTC
Duration
22h 15m
Affected: Hypernode Toolset / API / Control Panel
Timeline · 4 updates
  1. investigating Feb 24, 2026, 09:59 AM UTC

    We are currently experiencing degraded performance in the control panel. This issue has been caused by a portion of our non-critical infrastructure reaching resource limits. While the Hypernodes remain operational, users may notice slower or no responses when using the control panel. Our engineering team is actively working to resolve the capacity constraints and restore full performance. We expect operations to return to normal shortly.

  2. monitoring Feb 24, 2026, 10:08 AM UTC

    A fix has been implemented and the problems in the control panel have been resolved, we will further monitor the situation.

  3. monitoring Feb 24, 2026, 10:09 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 25, 2026, 08:15 AM UTC

    Issues has been fixed we don't expect this to occur again

Read the full incident report →

Looking to track Hypernode downtime and outages?

Pingoru polls Hypernode's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Hypernode reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Hypernode alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Hypernode for free

5 free monitors · No credit card required