Histórico de interrupções do Hypernode

1. 1 Eost 2026 da 10:05 UTCidentified

   Estamos experimentando uma falha no DNS causada por um ataque DDoS visando a infraestrutura do nosso parceiro de hospedagem DNS. Estão a diagnosticar e a mitigar o ataque. Estamos em contacto com a equipa deles e a monitorizar a situação. Atualizaremos assim que o serviço for restaurado.

2. 1 Eost 2026 da 11:17 UTCmonitoring

   A equipe colocou mitigação contra o ataque DDOS e estará acompanhando de perto a situação.

3. 1 Eost 2026 da 13:05 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Gouere 2026 da 09:40 UTCinvestigating

   Atualmente estamos experimentando alguma degradação ao fazer alterações em Hypernodes (alterações de versão, listas brancas, chaves SSH). Contacte o suporte para casos urgentes. Isto não influencia a disponibilidade geral para o seu servidor ou aplicação.

2. 9 Gouere 2026 da 09:51 UTCmonitoring

   Uma correção foi removida e as mudanças perdidas serão agora tratadas, por favor, fique de olho no `hypernode-log' para quaisquer ações perdidas.

3. 9 Gouere 2026 da 10:36 UTCmonitoring

   Todos os sistemas operacionais. Uma sincronização primitiva no nosso sistema de automação ficou presa num estado morto. Estamos implementando regras de monitoramento para identificar questões semelhantes no futuro, enquanto continuamos monitorando o sistema para fechaduras mortas.

4. 9 Gouere 2026 da 10:37 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Ebrel 2026 da 12:18 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. 14 Ebrel 2026 da 12:28 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. 14 Ebrel 2026 da 13:15 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. 13 Ebrel 2026 da 09:26 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. 13 Ebrel 2026 da 09:36 UTCmonitoring

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

3. 13 Ebrel 2026 da 12:53 UTCresolved

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

1. 24 Meurzh 2026 da 10:45 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. 24 Meurzh 2026 da 15:13 UTCidentified

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

3. 24 Meurzh 2026 da 19:23 UTCmonitoring

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

4. 25 Meurzh 2026 da 12:17 UTCresolved

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

1. 24 Cʼhwevrer 2026 da 09:59 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. 24 Cʼhwevrer 2026 da 10:08 UTCmonitoring

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

3. 24 Cʼhwevrer 2026 da 10:09 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 25 Cʼhwevrer 2026 da 08:15 UTCresolved

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

1. 1 Cʼhwevrer 2026 da 22:09 UTCinvestigating

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

2. 1 Cʼhwevrer 2026 da 22:34 UTCidentified

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

3. 1 Cʼhwevrer 2026 da 22:47 UTCresolved

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

1. 16 Kerzu 2025 da 15:46 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. 15 Kerzu 2025 da 07:57 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. 15 Kerzu 2025 da 17:18 UTCresolved

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

1. 12 Kerzu 2025 da 12:00 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. 12 Kerzu 2025 da 15:28 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. 5 Kerzu 2025 da 09:06 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. 5 Kerzu 2025 da 09:19 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. 18 Du 2025 da 12:05 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. 18 Du 2025 da 14:45 UTCresolved

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

1. 16 Du 2025 da 16:57 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. 16 Du 2025 da 17:38 UTCidentified

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

3. 16 Du 2025 da 18:19 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. 16 Du 2025 da 20:01 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. 17 Du 2025 da 08:35 UTCresolved

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

1. 5 Du 2025 da 17:17 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. 5 Du 2025 da 19:23 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. 23 Here 2025 da 08:35 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. 23 Here 2025 da 08:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 23 Here 2025 da 08:44 UTCidentified

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

4. 23 Here 2025 da 08:49 UTCmonitoring

   Operational activities are being restored across the nodes.

5. 23 Here 2025 da 09:14 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. 15 Gwengolo 2025 da 14:18 UTCinvestigating

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

2. 15 Gwengolo 2025 da 14:37 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. 15 Gwengolo 2025 da 15:28 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. 10 Gwengolo 2025 da 11:06 UTCidentified

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

2. 10 Gwengolo 2025 da 13:15 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. 10 Gwengolo 2025 da 16:03 UTCresolved

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

1. 12 Eost 2025 da 16:20 UTCidentified

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

2. 12 Eost 2025 da 16:34 UTCresolved

   This incident has been resolved.

1. 25 Gouere 2025 da 07:40 UTCinvestigating

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

2. 25 Gouere 2025 da 09:04 UTCidentified

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

3. 25 Gouere 2025 da 12:23 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. 18 Mezheven 2025 da 08:04 UTCidentified

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

2. 18 Mezheven 2025 da 09:21 UTCresolved

   This incident has been resolved.