Historial de interrupciones de Hypernode

1. August 1, 2026 at 10:05 AM UTCidentified

   Estamos experimentando una salida DNS causada por un ataque DDoS dirigido a la infraestructura de nuestro socio de hospedaje DNS. Están diagnosticando y mitigando activamente el ataque. Estamos en estrecho contacto con su equipo y vigilando la situación. Actualizaremos tan pronto como el servicio sea restaurado.

2. August 1, 2026 at 11:17 AM UTCmonitoring

   El equipo ha colocado medidas de mitigación contra el ataque de DDOS y vigilará de cerca la situación.

3. August 1, 2026 at 1:05 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 9, 2026 at 9:40 AM UTCinvestigating

   Actualmente estamos experimentando cierta degradación al hacer cambios a Hypernodes (cambios de inversión, listas blancas, claves SSH). Por favor contacte con soporte para casos urgentes. Esto no influye en la disponibilidad general para su servidor o aplicación.

2. July 9, 2026 at 9:51 AM UTCmonitoring

   Una solución ha sido lanzada y los cambios perdidos se manejarán ahora, por favor mantenga un ojo hacia fuera en el 'hipernode-log' para cualquier acción perdida.

3. July 9, 2026 at 10:36 AM UTCmonitoring

   Todos los sistemas operativos. Una sincronización primitiva en nuestro sistema de automatización se atascó en un estado muerto. Estamos implementando reglas de monitoreo para identificar problemas similares en el futuro, mientras seguimos monitorizando el sistema para bloqueos muertos.

4. July 9, 2026 at 10:37 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. April 14, 2026 at 12:18 PM UTCidentified

   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. April 14, 2026 at 12:28 PM UTCmonitoring

   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. April 14, 2026 at 1:15 PM UTCresolved

   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.

1. April 13, 2026 at 9:26 AM UTCidentified

   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. April 13, 2026 at 9:36 AM UTCmonitoring

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

3. April 13, 2026 at 12:53 PM UTCresolved

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

1. March 24, 2026 at 10:45 AM UTCinvestigating

   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. March 24, 2026 at 3:13 PM UTCidentified

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

3. March 24, 2026 at 7:23 PM UTCmonitoring

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

4. March 25, 2026 at 12:17 PM UTCresolved

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

1. February 24, 2026 at 9:59 AM UTCinvestigating

   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. February 24, 2026 at 10:08 AM UTCmonitoring

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

3. February 24, 2026 at 10:09 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. February 25, 2026 at 8:15 AM UTCresolved

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

1. February 1, 2026 at 10:09 PM UTCinvestigating

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

2. February 1, 2026 at 10:34 PM UTCidentified

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

3. February 1, 2026 at 10:47 PM UTCresolved

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

1. December 16, 2025 at 3:46 PM UTCresolved

   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.

1. December 15, 2025 at 7:57 AM UTCidentified

   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. December 15, 2025 at 5:18 PM UTCresolved

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

1. December 12, 2025 at 12:00 PM UTCidentified

   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. December 12, 2025 at 3:28 PM UTCresolved

   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.

1. December 5, 2025 at 9:06 AM UTCidentified

   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. December 5, 2025 at 9:19 AM UTCresolved

   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.

1. November 18, 2025 at 12:05 PM UTCinvestigating

   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. November 18, 2025 at 2:45 PM UTCresolved

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

1. November 16, 2025 at 4:57 PM UTCinvestigating

   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. November 16, 2025 at 5:38 PM UTCidentified

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

3. November 16, 2025 at 6:19 PM UTCidentified

   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. November 16, 2025 at 8:01 PM UTCmonitoring

   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. November 17, 2025 at 8:35 AM UTCresolved

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

1. November 5, 2025 at 5:17 PM UTCinvestigating

   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. November 5, 2025 at 7:23 PM UTCresolved

   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.

1. October 23, 2025 at 8:35 AM UTCinvestigating

   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. October 23, 2025 at 8:35 AM UTCinvestigating

   We are continuing to investigate this issue.

3. October 23, 2025 at 8:44 AM UTCidentified

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

4. October 23, 2025 at 8:49 AM UTCmonitoring

   Operational activities are being restored across the nodes.

5. October 23, 2025 at 9:14 AM UTCresolved

   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.

1. September 15, 2025 at 2:18 PM UTCinvestigating

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

2. September 15, 2025 at 2:37 PM UTCmonitoring

   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. September 15, 2025 at 3:28 PM UTCresolved

   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.

1. September 10, 2025 at 11:06 AM UTCidentified

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

2. September 10, 2025 at 1:15 PM UTCmonitoring

   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. September 10, 2025 at 4:03 PM UTCresolved

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

1. August 12, 2025 at 4:20 PM UTCidentified

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

2. August 12, 2025 at 4:34 PM UTCresolved

   This incident has been resolved.

1. July 25, 2025 at 7:40 AM UTCinvestigating

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

2. July 25, 2025 at 9:04 AM UTCidentified

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

3. July 25, 2025 at 12:23 PM UTCresolved

   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.

1. June 18, 2025 at 8:04 AM UTCidentified

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

2. June 18, 2025 at 9:21 AM UTCresolved

   This incident has been resolved.