Hypernode Outage History

Started Oct 28, 2026, 04:05 PM UTC· resolved Oct 28, 2026, 07:03 PM UTC

1. investigating Oct 28, 2026, 04:05 PM UTC

   We are aware of the issues currently affecting our platform, which appear to be DNS-related. Our infrastructure partner is treating this as a top priority and is actively working to resolve the issue. We understand that these disruptions are impacting your operations, and we sincerely apologize for the inconvenience. We are doing everything we can to restore the service as quickly as possible.

2. identified Oct 28, 2026, 04:22 PM UTC

   If your DNS configuration makes use a CNAME record ending in hypernode.io, the hostname may currently fail to resolve, resulting in downtime for the affected domains. Customers who have configured their DNS using an IPv4 A record are not affected by this issue. If possible, we recommend temporarily replacing your CNAME record with an A record pointing to the appropriate IP address to restore your environment. Please ensure you use the correct IP address for your Hypernode. You can find this by using the following bash command: ``` dig -t A yournode.hypernode.io @nsa.byte.nl +short ``` In the meantime, we remain in close contact with our infrastructure provider and are actively monitoring the situation while they work on a resolution. The Hypernode Team

3. monitoring Oct 28, 2026, 04:36 PM UTC

   Earlier, we experienced issues with the nameservers at our infrastructure partner. It has since become clear that these issues were caused by a DDoS attack targeting the nameservers. The attack now appears to have calmed down, and we are seeing operations return to normal levels. We will continue to monitor the situation closely to ensure everything remains stable. For now, things are looking good, and we don't expect any further issues in the short term. We will provide another update if the situation changes.

4. resolved Oct 28, 2026, 07:03 PM UTC

   We have not observed any further DDoS activity targeting the infrastructure nameservers. The situation remains stable, and services are operating normally.

Read the full incident report →

Started Oct 21, 2026, 09:39 AM UTC· resolved Oct 29, 2026, 03:47 PM UTC

1. identified Oct 21, 2026, 09:39 AM UTC

   Hypernode is addressing two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, announced on October 21, 2026. Under certain conditions, these vulnerabilities could allow attackers to execute malicious code. - Platform-wide mitigation: Hypernode has deployed additional PHP configuration settings across all nodes: - session.upload_progress.enabled = 0 - session.use_strict_mode = 1 - Security patches: Corrected PHP packages will be installed as soon as they become available for the relevant PHP versions. - Extended support: Customers using older PHP versions with Hypernode PHP Extended Support are also covered. - Customer impact: No customer action is required. Customers should not revert the temporary PHP settings themselves. - Potential disruption: PHP restarts may cause brief interruptions, but Hypernode aims to minimise any impact on store availability. The configuration changes are temporary mitigations and do not replace the official security patches.

2. identified Oct 21, 2026, 11:46 AM UTC

   Due to a current PHP security vulnerability, Hypernode will perform emergency maintenance today. Starting at 14:30 CEST, your Hypernode will be temporarily taken offline, and a maintenance page will be displayed instead of your website. The official PHP security patches are scheduled for release at 15:00 CEST (13:00 UTC). Once the patches have been released and successfully applied, and we have verified that the environment is safe, we will bring your Hypernode back online. We expect the maintenance to last until approximately 15:30 CEST (13:30 UTC). However, if the official patches are delayed or additional time is required to apply them, the maintenance may take longer. No action is required on your part. We will handle the necessary updates and restore your Hypernode as soon as it is safe to do so. Please monitor our status page for updates throughout the maintenance: https://www.hypernode-status.com/ We apologise for the inconvenience and appreciate your understanding as we take the necessary measures to protect your environment.

3. identified Oct 21, 2026, 01:25 PM UTC

   Update on PHP Security Patches We are still waiting for the official PHP patches to become available. The expected end of maintenance has been extended to 16:30 CEST. In the meantime, the temporary security measures remain in place on all Hypernodes to mitigate the vulnerabilities. Once the official patches are released, we will apply them as soon as possible and bring any affected Hypernodes back online. No action is required from your side. We will keep you updated as soon as we have more information.

4. identified Oct 21, 2026, 01:45 PM UTC

   Update on PHP Security Patches The official PHP security patches for CVE-2026-109618 and CVE-2026-109619 are now available. We are currently working on implementing the patches on the Hypernode platform and will start rolling them out across our infrastructure shortly. Once the patches have been successfully applied to your Hypernode, we will bring it back online as soon as possible. We will keep you updated on the progress and notify you when the maintenance is completed. Thank you for your patience and understanding.

5. identified Oct 21, 2026, 02:34 PM UTC

   Update on PHP Security Patches We are currently rolling out the official PHP security patches across the Hypernode platform. We expect the first websites to be back online by 16:45 CEST. The rollout will continue across the remaining Hypernodes, and we will bring each site back online as soon as the patches have been successfully applied. We appreciate your patience and will keep you updated on further progress.

6. identified Oct 21, 2026, 02:52 PM UTC

   Update on PHP Security Patches We are now bringing Hypernodes running PHP 8.2 through PHP 8.5 out of maintenance mode. At the same time, we are actively applying the security patches to the EOL PHP versions across the Hypernode platform. These Hypernodes will be brought back online as soon as the patches have been successfully applied. We will continue monitoring the rollout and keep you updated on further progress. Thank you for your patience and understanding.

7. identified Oct 21, 2026, 04:18 PM UTC

   Update on PHP Security Patches Most servers running PHP 8.2 through PHP 8.5 have now been successfully updated and are back online. If your website is still in maintenance mode or is not accessible, please let us know so we can investigate. For the EOL PHP versions, we are still waiting for the required patch packages to become available. As soon as these packages are released, we will proceed with applying the patches and bringing the remaining affected servers back online. Thank you for your patience and understanding. We will share another update as soon as we have further news.

8. monitoring Oct 21, 2026, 06:33 PM UTC

   PHP Security Patches Completed All PHP versions on the Hypernode platform have now been successfully patched for the vulnerabilities CVE-2026-109618 and CVE-2026-109619. The rollout is complete across all supported and End-of-Life (EOL) PHP versions. Thank you for your patience and understanding throughout the maintenance. We apologize for any inconvenience caused.

9. monitoring Oct 22, 2026, 09:56 AM UTC

   Update: Platform Status Hypernode is fully operational again, and all PHP versions have been patched. We are still working on the remaining updates for Hipex and will provide another update as soon as there is further progress.

10. resolved Oct 29, 2026, 03:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Oct 13, 2026, 06:46 AM UTC· resolved Oct 13, 2026, 09:24 AM UTC

1. identified Oct 13, 2026, 06:46 AM UTC

   This issue has been identified, and a fix is being implemented.

2. monitoring Oct 13, 2026, 08:32 AM UTC

   A fix has been implemented and is being monitored

3. resolved Oct 13, 2026, 09:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 01, 2026, 10:05 AM UTC· resolved Aug 01, 2026, 01:05 PM UTC

1. identified Aug 01, 2026, 10:05 AM UTC

   We're experiencing a DNS outage caused by a DDoS attack targeting our DNS hosting partner's infrastructure. They are actively diagnosing and mitigating the attack. We're in close contact with their team and monitoring the situation. We'll update as soon as service is restored.

2. monitoring Aug 01, 2026, 11:17 AM UTC

   The team have placed mitigations against the DDOS attack and will be monitoring the situation closely.

3. resolved Aug 01, 2026, 01:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 09, 2026, 09:40 AM UTC· resolved Jul 09, 2026, 10:37 AM UTC

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.

Read the full incident report →

Started Apr 14, 2026, 12:18 PM UTC· resolved Apr 14, 2026, 01:15 PM UTC

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 →

Started Apr 13, 2026, 09:26 AM UTC· resolved Apr 13, 2026, 12:53 PM UTC

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 →

Started Mar 24, 2026, 10:45 AM UTC· resolved Mar 25, 2026, 12:17 PM UTC

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 →

Started Feb 24, 2026, 09:59 AM UTC· resolved Feb 25, 2026, 08:15 AM UTC

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 →

Started Feb 01, 2026, 10:09 PM UTC· resolved Feb 01, 2026, 10:47 PM UTC

1. investigating Feb 01, 2026, 10:09 PM UTC

   We are experience with our Object Storage service provider. Investigation with provider is ongoing.

2. identified Feb 01, 2026, 10:34 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Feb 01, 2026, 10:47 PM UTC

   This incident has been resolved by our Object Storage service provider.

Read the full incident report →

Started Dec 16, 2025, 03:15 AM UTC· resolved Dec 16, 2025, 03:30 AM UTC

1. resolved Dec 16, 2025, 03:15 AM UTC

   We experienced a brief network hiccup in one of our datacenters, which may have caused intermittent connectivity issues for approximately 15 minutes. The issue has been resolved, and network stability has been fully restored. Our team monitored the situation closely to ensure no further impact. No further action is required at this time. We will continue to monitor the platform to ensure ongoing stability.

Read the full incident report →

Started Dec 15, 2025, 07:57 AM UTC· resolved Dec 15, 2025, 05:18 PM UTC

1. identified Dec 15, 2025, 07:57 AM UTC

   We are currently aware of an issue affecting the control panel on my.hypernode.com. Some users may experience problems loading the “My Hypernodes” page. Our team is investigating the issue and working to determine the cause. At this time, no other services appear to be impacted.

2. resolved Dec 15, 2025, 05:18 PM UTC

   The issue affecting the "My Hypernodes” page has been isolated and resolved. All services are now operating normally.

Read the full incident report →

Started Dec 12, 2025, 12:00 PM UTC· resolved Dec 12, 2025, 03:28 PM UTC

1. identified Dec 12, 2025, 12:00 PM UTC

   We are currently experiencing an issue with our control panel on my.hypernode.com. The “My Hypernodes” page is not functioning correctly, and the list of Hypernodes is not loading. Our team is aware of the issue and is actively investigating the cause. At this time, no other services are impacted. We will provide an update as soon as more information becomes available.

2. resolved Dec 12, 2025, 03:28 PM UTC

   The issue affecting the control panel on my.hypernode.com, where the “My Hypernodes” page was not loading correctly, has been resolved. All functionality is operating normally again, and no other services were impacted. We will continue to monitor the platform to ensure stability.

Read the full incident report →

Started Dec 05, 2025, 09:06 AM UTC· resolved Dec 05, 2025, 09:19 AM UTC

1. identified Dec 05, 2025, 09:06 AM UTC

   We are currently experiencing issues with several services due to a broader Cloudflare disruption. This outage is affecting our Support ticketing system, and our phone support is currently unavailable. Additionally, some customers may experience 500 errors on their websites as a result of this Cloudflare issue. Cloudflare is currently investigating problems impacting the Cloudflare Dashboard and related APIs. Customers using the Dashboard or API functionality may encounter failed requests or error messages.

2. resolved Dec 05, 2025, 09:19 AM UTC

   Cloudflare has resolved the underlying issue, and all our services are fully operational again. We have confirmed that both our Support systems and phone availability are functioning normally.

Read the full incident report →

Started Nov 18, 2025, 12:05 PM UTC· resolved Nov 18, 2025, 02:45 PM UTC

1. investigating Nov 18, 2025, 12:05 PM UTC

   Cloudflare is currently experiencing issues routing requests to some Hypernodes. Please note that this is not a Hypernode outage, and the issue must be resolved on Cloudflare’s side. We recommend keeping an eye on Cloudflare’s status page for updates. If this significantly impacts you, a temporary workaround is to disable the Cloudflare Proxy in your Cloudflare DNS settings until the issue is resolved.

2. resolved Nov 18, 2025, 02:45 PM UTC

   The incident has been marked as resolved by Cloudflare and we're expecting no more inconvenience.

Read the full incident report →

Started Nov 16, 2025, 04:57 PM UTC· resolved Nov 17, 2025, 08:35 AM UTC

1. investigating Nov 16, 2025, 04:57 PM UTC

   We're currently seeing extremely degraded performance across our platform, this seems to be related to our DNS resolving to hypernode.io , we are actively investigating and will update when possible.

2. identified Nov 16, 2025, 05:38 PM UTC

   We have identified our DNS server is being flooded with packets. We are activating our counter-measures and continue monitoring the situation.

3. identified Nov 16, 2025, 06:19 PM UTC

   Sadly as we're trying to resolve this as quick we can, an alternative temporary solution is to use the direct IP if you're using an external DNS service, you can get this with using dig with our alternative DNS server, make sure to point your A-record to the resulting IP-address: ``` dig @80.84.227.137 abc.hypernode.io A ``` We hope this won't be needed for long and we can return operations as soon as possible.

4. monitoring Nov 16, 2025, 08:01 PM UTC

   As the attack seems to calm down, operations are returning on our nodes and internal infrastructure. We continue working on increasing our stability to mitigate future incidents.

5. resolved Nov 17, 2025, 08:35 AM UTC

   Our DNS infrastructure has been running stable for the past 12 hours. We'll continue to monitor and improve the infrastructure.

Read the full incident report →

Started Nov 05, 2025, 05:17 PM UTC· resolved Nov 05, 2025, 07:23 PM UTC

1. investigating Nov 05, 2025, 05:17 PM UTC

   We're currently seeing degraded performance for our Cloudflare users running on at least our German dedicated datacenter, we are monitoring the situation and are contact with the relevant third parties

2. resolved Nov 05, 2025, 07:23 PM UTC

   We're seeing no current problems on the datacenter/Hypernode side, and it appears to be an instability with Cloudflare. Please be advised to consider disabling the proxy temporarily and monitoring the situation closely.

Read the full incident report →

Started Oct 23, 2025, 08:35 AM UTC· resolved Oct 23, 2025, 09:14 AM UTC

1. investigating Oct 23, 2025, 08:35 AM UTC

   The Hypernode cloud platform for the R405 room is currently experiencing degraded performance and may cause incididental downtime, we are aware of this and are monitoring the situation. As soon as we know more we will update our statuspage.

2. investigating Oct 23, 2025, 08:35 AM UTC

   We are continuing to investigate this issue.

3. identified Oct 23, 2025, 08:44 AM UTC

   Our provider has identified the issue and is working on a solution

4. monitoring Oct 23, 2025, 08:49 AM UTC

   Operational activities are being restored across the nodes.

5. resolved Oct 23, 2025, 09:14 AM UTC

   All affected nodes have fully resumed operations. Earlier, our cloud provider in Room R405 experienced a temporary issue with their network-storage layer, which caused downtime on these nodes. The provider quickly diagnosed and resolved the problem. We confirm that no data loss occurred.

Read the full incident report →

Started Sep 15, 2025, 02:18 PM UTC· resolved Sep 15, 2025, 03:28 PM UTC

1. investigating Sep 15, 2025, 02:18 PM UTC

   We are aware of issues with the Cloud Hypernodes and are in close contact with the datacenter to determine the cause.

2. monitoring Sep 15, 2025, 02:37 PM UTC

   We identified a brief downtime in one of the OpenStack availability zones, which triggered our monitoring systems to automatically reboot some nodes. Platform stability is now improving and returning to normal.

3. resolved Sep 15, 2025, 03:28 PM UTC

   A brief network interruption in one of our OpenStack availability zones caused some instances to automatically reboot. The issue has been resolved and platform stability has been restored.

Read the full incident report →

Started Sep 10, 2025, 11:06 AM UTC· resolved Sep 10, 2025, 04:03 PM UTC

1. identified Sep 10, 2025, 11:06 AM UTC

   We are currently experiencing DNS disruptions caused by a DDoS attack. This has resulted in intermittent service issues for some users.

2. monitoring Sep 10, 2025, 01:15 PM UTC

   We've taken measures on our side to help mitigate the impact of the DDoS attack on our DNS infrastructure. At this time, full performance has been restored, and we are closely monitoring the situation.

3. resolved Sep 10, 2025, 04:03 PM UTC

   The issue has now been fully resolved, and all services are operating normally.

Read the full incident report →

Started Aug 12, 2025, 04:20 PM UTC· resolved Aug 12, 2025, 04:34 PM UTC

1. identified Aug 12, 2025, 04:20 PM UTC

   The issue has been identified and a fix is being implemented.

2. resolved Aug 12, 2025, 04:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 25, 2025, 07:40 AM UTC· resolved Jul 25, 2025, 12:23 PM UTC

1. investigating Jul 25, 2025, 07:40 AM UTC

   We are currently experiencing issues with creating branchers, xgrading and providing ordered Hypernodes. Our team is actively investigating and resolving this issue.

2. identified Jul 25, 2025, 09:04 AM UTC

   The issue has been identified and we are working on a fix.

3. resolved Jul 25, 2025, 12:23 PM UTC

   The issue has been resolved and had to do with resource-limitations with our service partners, we will be monitoring the situation over the coming week but do not expect any downtime at this current moment.

Read the full incident report →

Started Jun 18, 2025, 08:04 AM UTC· resolved Jun 18, 2025, 09:21 AM UTC

1. identified Jun 18, 2025, 08:04 AM UTC

   We are currently experiencing issues in updating, xgrading and providing ordered Hypernodes. Our team is actively investigating and resolving this issue.

2. resolved Jun 18, 2025, 09:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 27, 2025, 09:43 AM UTC· resolved May 27, 2025, 01:03 PM UTC

1. investigating May 27, 2025, 09:43 AM UTC

   We are currently observing degraded performance on the Control Panel homepage and Hypernode Insights. Certain components that display statistics are failing to load correctly. All APIs and other parts of the Control Panel/Hypernode Insights remain fully operational. Our team is actively investigating the issue.

2. resolved May 27, 2025, 01:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 04, 2025, 10:13 AM UTC· resolved Feb 04, 2025, 11:17 AM UTC

1. identified Feb 04, 2025, 10:13 AM UTC

   Let's Encrypt recently implemented a change that disrupted our certificate renewal process for Let's Encrypt certificates. We have implemented a fix and are working on a platform-wide resolution. Possible errors include mozilla_pkix_error_required_tls_feature_missing and occasional issues when requesting a new certificate via Hypernode Manage vhosts.

2. identified Feb 04, 2025, 10:13 AM UTC

   We are continuing to work on a fix for this issue.

3. resolved Feb 04, 2025, 11:17 AM UTC

   The recent Let's Encrypt change that disrupted our certificate renewal process has been fully resolved platform-wide. Users should no longer experience issues, including the mozilla_pkix_error_required_tls_feature_missing error or problems requesting new certificates via Hypernode Manage vhosts. If you continue to encounter any issues, please reach out to support.

Read the full incident report →