NovaCloud-Hosting - Notice history

All systems operational

Website - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2026
May 2026
Jun 2026

Dashboard - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2026
May 2026
Jun 2026
Operational

Game-Panel - Operational

100% - uptime
Apr 2026 · 100.0%May · 99.70%Jun · 100.0%

Previous page

Next page

Apr 2026
May 2026
Jun 2026

Dedicated-Server Management - Operational

100% - uptime
Apr 2026 · 100.0%May · 99.92%Jun · 100.0%

Previous page

Next page

Apr 2026
May 2026
Jun 2026
Operational

Dedicated-Server EYG1 - Operational

Operational

Dedicated-Server NBG1 - Operational

Notice history

Jun 2026

XEON03-VHOST-EYG1 outage
  • Resolved
    Resolved

    All affected virtual servers have now been successfully started and are operating normally. The incident has been resolved.

    If you continue to experience any issues with your service, please contact us immediately by emailing support@novacloud-hosting.com or by opening a support ticket through the customer dashboard.

    As compensation for the downtime, all affected customers will receive 3 days of additional service time. This compensation will be applied automatically within the next 48 hours, and we will send an email notification to all affected customers once it has been processed.

    We sincerely apologize for the inconvenience caused by this unexpected hardware failure and would like to thank you for your patience and understanding throughout the incident.

  • Monitoring
    Monitoring

    The defective motherboard has been successfully replaced by aa technician, and the server is now back online.

    All VPS are currently starting up and services are being restored. Based on our checks, there has been no data loss as a result of this incident.

    We will continue to monitor the system closely over the next few hours to ensure everything remains stable.

    We sincerely apologize for the inconvenience caused and thank you for your patience throughout this incident.

  • Update
    Update

    The technician has completed further diagnostics and replaced all RAM modules, CPU1, and the cooling fans. Unfortunately, none of these measures resolved the issue.

    Based on the diagnostics, the root cause has been identified as a defective motherboard. Replacing the motherboard is a more time-consuming procedure and requires more time. As a result, the replacement will be carried out by the regular datacenter shift on Monday morning.

    We will provide another update as soon as the replacement has been completed or new information becomes available.

  • Update
    Update

    A technician is currently on the way to the datacenter to perform further diagnostics and, if possible, replace the defective hardware on-site. We will provide another update as soon as we have more information.

  • Update
    Update

    We have identified a hardware issue affecting the XEON03-VHOST-EYG1 hostsystem.

    Initial diagnostics indicate a possible failure of either the motherboard or CPU, as CPU1 is unable to detect any installed memory modules. Additionally, the server performed an automatic shutdown after multiple cooling fans failed within a 15-minute timeframe.

    We have already contacted the datacenter and are currently awaiting their response. Based on the current situation, we unfortunately do not expect the issue to be resolved before Monday morning.

    We sincerely apologize for the inconvenience caused by this unexpected hardware failure. While incidents of this nature cannot be predicted or prevented, we understand the impact they have on your services and are working with the highest priority to restore the service as quickly as possible.

    As compensation for the downtime, all affected customers will receive an extension of their service once the incident has been fully resolved.

    Please note that, due to the ongoing incident, support tickets related to it will be processed on a limited basis until normal operations have been restored. We will continue to provide updates here as new information becomes available.

  • Identified
    Identified

    It seems that the server orderly shutdown for a currently unknown reason. There is no hardware fault and the server is currently starting.

  • Investigating
    Investigating
    We are currently investigating this incident.
EPYC-01-VHOST Memory Replacement
  • Completed
    15 June, 2026 at 10:17 AM
    Completed
    15 June, 2026 at 10:17 AM

    All VPS are online since 11:43 UTC. If you still experience issues, please immediately create a ticket or send an email to support@novacloud-hosting.com.

    We apologize for any inconvenience caused by this maintenance and thank for your continued trust in our services.

  • Update
    15 June, 2026 at 9:34 AM
    Update
    15 June, 2026 at 9:34 AM

    The maintenance is now complete and all VPS are gradually starting up. We expect all VPS to be available in around 5-15 minutes and will provide an update.

  • Update
    15 June, 2026 at 8:56 AM
    Update
    15 June, 2026 at 8:56 AM

    We are now starting with the replacement of the defective hardware and will shutdown all VMs on the hostsystem.

  • In progress
    15 June, 2026 at 7:00 AM
    In progress
    15 June, 2026 at 7:00 AM
    Maintenance is now in progress
  • Update
    12 June, 2026 at 4:23 PM
    Update
    12 June, 2026 at 4:23 PM

    We have to postpone the planned maintenance to 15.06.2026 between 9:00-13 UTC. Thanks for your understanding.

  • Planned
    11 June, 2026 at 10:46 PM
    Planned
    11 June, 2026 at 10:46 PM

    Emergency Maintenance

    We will perform an emergency maintenance on EPYC-01-VHOST to replace multiple defective memory modules.

    During the previous incident, one faulty memory module was successfully disabled during the reboot process. However, we have since identified an additional defective module that was not automatically disabled and is continuing to generate memory errors. While the system is currently operational, it cannot be considered fully stable in its current state.

    To prevent an unexpected outage and ensure long-term stability, we have decided to replace the affected hardware as soon as possible.

    Schedule

    We are currently planning to perform the maintenance on 13 June 2026 between 9:00 and 12:00 CEST.

    Expected Impact

    • Temporary service interruption of all Premium VPS (AMD EPYC VPS) during the maintenance window

    • Expected maintenance duration: up to 30 minutes

    • Services will automatically resume once the replacement has been completed

    We apologize for the short notice and any inconvenience this emergency maintenance may cause.

FFM2 Network Improvements
  • Update
    13 June, 2026 at 2:26 PM
    Update
    13 June, 2026 at 2:26 PM

    i was meaning IPv4 downtime was minimal with under 2 minutes :D

  • Completed
    13 June, 2026 at 2:26 PM
    Completed
    13 June, 2026 at 2:26 PM

    Maintenance has completed successfully.

    We had some issues with IPv6 after migration, which has been fixed after around 10 minutes downtime.

    IPv4 downtime was minimal, under 2 minutes.

  • In progress
    13 June, 2026 at 12:00 PM
    In progress
    13 June, 2026 at 12:00 PM
    Maintenance is now in progress
  • Planned
    12 June, 2026 at 3:59 AM
    Planned
    12 June, 2026 at 3:59 AM

    Scheduled: 13 June 2026, 14:00–17:00 CEST

    To address the increased latency and packet loss that some customers have experienced during periods of high network utilization since the migration from FFM1 to FFM2, we will be performing network maintenance during the above window.

    As part of this maintenance, we will:

    • Increase the router's available bandwidth capacity

    • Replace the temporary router currently in service with a permanent production router

    Expected Impact

    A brief service interruption may occur for affected services while traffic is migrated to the upgraded infrastructure.

    Under normal circumstances, we expect the interruption to last less than one minute. However, should any unexpected issues arise during the maintenance, the outage may be extended while corrective actions are performed.

    Why This Maintenance Is Being Performed

    We have decided to schedule this maintenance on short notice to resolve the latency and packet loss issues as quickly as possible and improve the overall stability and performance of our FFM2 network infrastructure.

    We apologize for any inconvenience this maintenance may cause and appreciate your understanding.

EPYC-VHOST-01 outage
  • Resolved
    Resolved

    All affected VPS are now back online and operating normally.

    If you continue to experience any issues, please open a support ticket or contact us via email at support@novacloud-hosting.com.

  • Monitoring
    Monitoring

    All affected VPS are currently starting up. We expect all services to be fully operational again within approximately 15 minutes.

  • Identified
    Identified

    We have identified a defective RAM module in the affected host system. This caused the system to crash, as the number of memory errors exceeded what ECC could reliably correct.

    We are currently restarting the host system to bring all affected VPS back online. During the boot process, the system will automatically disable the faulty memory module to prevent further instability while a permanent hardware replacement is arranged.

    We apologize for the inconvenience and will provide further updates as necessary.

  • Investigating
    Investigating

    It seems that EPYC-VHOST-01 is unresponsible We are currently investigating this incident.

EYG1: Fiber connection to Frankfurt down
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    Today at 12:09 CEST, the DCI interconnection towards Frankfurt unexpectedly went down. Traffic was automatically rerouted within a few seconds, but customers with services located in EYG1 may have experienced brief interruptions for connections that were routed via Frankfurt.

    At the moment, affected EYG1 services may notice increased latency due to the rerouting, but no packetloss or connection issues. Services in all other locations remain unaffected.

    We are currently waiting for further updates from the upstream/provider and will provide another update once more information is available.

May 2026

EYG1 Partial Power maintenance
  • Completed
    29 May, 2026 at 6:15 AM
    Completed
    29 May, 2026 at 6:15 AM
    Maintenance has completed successfully
  • Planned
    29 May, 2026 at 5:30 AM
    Planned
    29 May, 2026 at 5:30 AM

    On Friday, 29 May 2026, starting at 07:30 AM (CEST), the datacenter will perform maintenance work on the power infrastructure to further improve resilience and ensure uninterrupted power availability in the event of a utility power outage.

    Most systems are connected to redundant power feeds and will not be affected. However, a limited number of servers require a restart during this maintenance because they are equipped with a single power supply and therefore cannot be connected to both power feeds simultaneously.

    The maintenance window is scheduled for a maximum duration of 45 minutes.

    A few minutes before the maintenance begins, we will perform a graceful shutdown of the affected servers and start them again once the work has been completed.

    The following dedicated servers are affected:

    • s200

    • s211

    • s249

    • s541

    • s628

    We apologize for any inconvenience this may cause and appreciate your understanding.

EYG1 Partial Power maintenance
  • Completed
    28 May, 2026 at 6:15 AM
    Completed
    28 May, 2026 at 6:15 AM
    Maintenance has completed successfully
  • In progress
    28 May, 2026 at 5:30 AM
    In progress
    28 May, 2026 at 5:30 AM
    Maintenance is now in progress
  • Planned
    28 May, 2026 at 5:30 AM
    Planned
    28 May, 2026 at 5:30 AM

    On Thursday, 28 May 2026, starting at 07:30 AM (CEST), the datacenter will perform maintenance work on the power infrastructure to further improve resilience and ensure uninterrupted power availability in the event of a utility power outage.

    Most systems are connected to redundant power feeds and will not be affected. However, a limited number of servers require a restart during this maintenance because they are equipped with a single power supply and therefore cannot be connected to both power feeds simultaneously.

    The maintenance window is scheduled for a maximum duration of 45 minutes.

    A few minutes before the maintenance begins, we will perform a graceful shutdown of the affected servers and start them again once the work has been completed.

    The following dedicated servers are affected:

    • s544

    • s553

    In addition, the following virtualization hosts are affected:

    • RYZEN-01-VHOST-EYG1

    • RYZEN-03-VHOST-EYG1

    • RYZEN-05-VHOST-EYG1

    Virtual machines hosted on these nodes will be unavailable for the duration of the maintenance window and will automatically start again once the host systems are back online.

    We apologize for any inconvenience this may cause and appreciate your understanding.

FFM2 network outage
  • Resolved
    Resolved

    A hardware defect on our upstream provider's core router caused a temporary outage at our FFM2 location. Due to a hard failure, a graceful switchover to the standby routing engine was not possible.

    A full reboot of the system was required, taking approximately 10 to 15 minutes. Following the startup, all BGP sessions successfully recovered. The location is now fully stable, and traffic has returned to normal. We sincerely apologize for the disruption.

  • Monitoring
    Monitoring

    We are seeing the network recovering. BGP Sessions are up again and network traffic is returning to normal levels. We have not received an official confirmation from our upstream yet.

  • Identified
    Identified

    Our Upstream has confirmed an outage of their network equipment of the NTT FRA1 site. A technician has been dispatched.

  • Investigating
    Investigating

    We are currently investigating this incident.

EYG1 Partial Power maintenance
  • Completed
    22 May, 2026 at 5:46 AM
    Completed
    22 May, 2026 at 5:46 AM
    Maintenance has completed successfully.
  • In progress
    22 May, 2026 at 5:45 AM
    In progress
    22 May, 2026 at 5:45 AM
    Maintenance is now in progress
  • Planned
    22 May, 2026 at 5:45 AM
    Planned
    22 May, 2026 at 5:45 AM

    On Friday, 22 May 2026, starting at 07:45 AM (CEST), the datacenter will perform maintenance work on the power infrastructure to further improve resilience and ensure uninterrupted power availability in the event of a utility power outage.

    Most systems are connected to redundant power feeds and will not be affected. However, a limited number of servers require a restart during this maintenance because they are equipped with a single power supply and therefore cannot be connected to both power feeds simultaneously.

    The maintenance window is scheduled for a maximum duration of 30 minutes.

    A few minutes before the maintenance begins, we will perform a graceful shutdown of the affected servers and start them again once the work has been completed.

    The following dedicated servers are affected:

    • s544

    • s553

    In addition, the following virtualization hosts are affected:

    • RYZEN-07-VHOST-EYG1

    • RYZEN-08-VHOST-EYG1

    Virtual machines hosted on these nodes will be unavailable for the duration of the maintenance window and will automatically start again once the host systems are back online.

    We apologize for any inconvenience this may cause and appreciate your understanding.

Network outage FFM2
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    The DDoS Attack is now being Mitigated and network reachability is normal again. We are actively monitoring the situation.

  • Identified
    Identified

    Our network has received a DDoS Attack on one of our unprotected subnets. We have taken measures to mitigate the DDoS Attack and are continously working on the issue.

  • Investigating
    Investigating
    We are currently investigating this incident.

Apr 2026

Planned Network Maintenance on 24.04.2026 at EYG1
  • Completed
    24 April, 2026 at 1:00 AM
    Completed
    24 April, 2026 at 1:00 AM
    Maintenance has completed successfully
  • In progress
    23 April, 2026 at 10:00 PM
    In progress
    23 April, 2026 at 10:00 PM
    Maintenance is now in progress
  • Planned
    23 April, 2026 at 10:00 PM
    Planned
    23 April, 2026 at 10:00 PM

    Scheduled Maintenance – EYG1 Upstream Connectivity

    Our upstream provider at the EYG1 location has announced short-notice maintenance affecting a transport link to Amsterdam. This maintenance is required to improve long-term network stability.

    Time window:
    April 24, 2026, 00:00 – 06:00 (UTC+2, CEST)
    Expected impact duration: ~2–3 hours within this window

    Expected impact:
    During the maintenance, you may experience:

    • Increased latency

    • Packet loss

    • Reduced bandwidth availability

    To mitigate impact, traffic will be partially rerouted via our Frankfurt PoP.

    Background:
    A similar maintenance took place on March 20, 2026. While we understand the inconvenience, these measures are necessary to improve upstream stability.

    We are currently finalizing a new redundant network PoP in Düsseldorf (Digital Realty), including a dedicated dark fiber connection. Once operational (planned for May 2026), this will eliminate the impact of similar upstream maintenance events in the future.

    We apologize for any inconvenience caused and appreciate your understanding.

Multiple Servers at EYG1 location unreachable
  • Postmortem
    Postmortem

    On the morning of April 23, a brief utility power failure occurred at the EYG1 data center. One of the Uninterruptible Power Supply (UPS) units failed to engage, causing a total loss of power on one of the power feeds. Servers equipped with only a single Power Supply Unit (PSU) connected to this feed experienced an immediate powerloss. While most systems recovered automatically, the host RYZEN-07-VHOST-EYG1 suffered a secondary hardware issue that required manual intervention.

    Root Cause Analysis

    1. Power Feed Failure: An external power dip was not mitigated by a specific UPS system, leading to a localized blackout on one power feed.

    2. Lack of Redundancy: Impacted Ryzen-based servers utilized non-redundant power configurations. Consequently, the loss of a single feed resulted in an immediate power loss for these machines.

    3. Hardware Damage: The abrupt shutdown triggered a hardware-level fault on host RYZEN-07-VHOST-EYG1, preventing it from rebooting autonomously.

    Incident Timeline

    • 09:33 AM: Monitoring alerts triggered for multiple host systems at EYG1. Investigation initiated.

    • 09:41 AM: Issue identified as a power feed failure. Most affected servers were already successfully restarted and entered monitoring status.

    • 09:56 AM: All systems recovered except for RYZEN-07-VHOST-EYG1. An on-site technician was dispatched to address the hardware failure.

    • 10:11 AM: Hardware repair completed. RYZEN-07-VHOST-EYG1 initiated startup, and all hosted VPS returned to online status shortly thereafter.

  • Resolved
    Resolved

    RYZEN-07-VHOST-EYG1 is now starting up. All VPS on it should be online within the next 5 minutes.

  • Identified
    Identified

    RYZEN-07-VHOST-EYG1 is currently still unreachable. A technitian has already been informed about this incident.

  • Monitoring
    Monitoring

    All affected servers have been started. It seems to be a power-related issue on one of the power feeds, which affected half the servers with non-redundant PSUs. Therefore only AMD Ryzen VPS in Netherlands were partially affected.

    If your server is still unreachable, please create a support ticket so we can address the issue.

  • Investigating
    Investigating

    Multiple of our Hostsystems at the EYG1 location are currently unreachable. We are investigating the issue.

EPYC-01-VHOST Memory replacement
  • Completed
    22 April, 2026 at 9:46 AM
    Completed
    22 April, 2026 at 9:46 AM
    Maintenance has completed successfully.
  • Update
    22 April, 2026 at 9:44 AM
    Update
    22 April, 2026 at 9:44 AM

    Defective ram issues is still not resolved we are counting to investigate the issue

  • In progress
    22 April, 2026 at 7:00 AM
    In progress
    22 April, 2026 at 7:00 AM
    Maintenance is now in progress
  • Planned
    22 April, 2026 at 7:00 AM
    Planned
    22 April, 2026 at 7:00 AM

    We are planning for a scheduled maintenance during that time to replace a defective Memory module. The actual maintenance is not planned to take longer than 30 minutes.

XEON-03-VHOST Memory replacement
  • Completed
    10 April, 2026 at 1:45 PM
    Completed
    10 April, 2026 at 1:45 PM
    Maintenance has completed successfully.
  • Update
    10 April, 2026 at 1:14 PM
    Update
    10 April, 2026 at 1:14 PM

    Due to some delays, we had to postpone the maintenance. It will be finished in approximately 30 minutes.

  • In progress
    10 April, 2026 at 8:00 AM
    In progress
    10 April, 2026 at 8:00 AM
    Maintenance is now in progress
  • Planned
    10 April, 2026 at 8:00 AM
    Planned
    10 April, 2026 at 8:00 AM

    We are planning for a scheduled maintenance during that time to replace a defective Memory module. The actual maintenance is not planned to take longer than 30 minutes.

Apr 2026 to Jun 2026

Next