<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.v6node.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.v6node.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.v6node.com/history.atom"/>
  <title>v6Node Status - Incident history</title>
  <updated>2026-02-04T12:16:00.000+00:00</updated>
  <author>
    <name>v6Node</name>
  </author>
  
<entry>
  <id>tag:status.v6node.com,2005:Incident/cml82nmnq00yygpz3a7qvc66i</id>
  <published>2026-02-04T12:16:00.000+00:00</published>
  <updated>2026-02-04T12:16:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cml82nmnq00yygpz3a7qvc66i"/>
  <title>Packet loss in Frankfurt</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 42 minutes</p>
    <p><strong>Affected Components:</strong> Virtualization Cluster Frankfurt, DE (FRA1), Virtualization Cluster Frankfurt, DE (FRA2)</p>
    <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>12:16:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We see packet loss in our FRA2 facility starting 13:16 (German time). While all nodes are running, you might experience issues accessing your node. The situation is being investigated and we will update this post when we have new information. .</p>
<p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>13:57:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/cml5t3wow00637zaqdfvg4pqt</id>
  <published>2026-02-02T23:26:00.000+00:00</published>
  <updated>2026-02-02T23:26:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cml5t3wow00637zaqdfvg4pqt"/>
  <title>Network outage in Frankfurt</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 hours and 59 minutes</p>
    
    <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>23:26:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are currently investigating a network outage with our upstream provider that is affecting our infrastructure in Frankfurt, Germany.  
  
Our upstream provider is working on their network and informed us about an outage during a planned maintenance activity. See here for details: &lt;https://status.dataforest.net/incidents/xst6r28991hy&gt;

We expected services to recover any minute..</p>
<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>23:32:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented by dataforest at 00:31 (German time), leading to recovery of our services. The situation is under control and will be analyzed further. We will update this post as soon as we have new information..</p>
<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>16:24:46</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/cmh3d13yn00ef3vlm6y68mw96</id>
  <published>2025-10-23T11:49:54.683+00:00</published>
  <updated>2025-10-23T11:49:54.683+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cmh3d13yn00ef3vlm6y68mw96"/>
  <title>Network Outage in Frankfurt</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> Virtualization Cluster Frankfurt, DE (FRA1), Website , Cloud Portal, Virtualization Cluster Frankfurt, DE (FRA2)</p>
    <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>11:49:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating a network outage with our upstream provider that is affecting our infrastructure in Frankfurt, Germany..</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>12:16:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  The network of our upstream provider was disconnected from 13:33 to 14:01 CEST, resulting in approximately 30 minutes of downtime for services in our FRA1/FRA2 data center.

The issue was caused by a software bug in their aggregation switches, which triggered a major outage during a routine edge network change related to ongoing DDoS mitigation efforts. Layer 2 connectivity was completely lost and could only be restored by rebooting the affected devices.

Connectivity was restored at 14:00 CEST, and BGP sessions have been stable since..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Maintenance/cmawcwoqv000lyusfox4nb9g3</id>
  <published>2025-05-24T02:00:00.000+00:00</published>
  <updated>2025-05-24T02:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/maintenance/cmawcwoqv000lyusfox4nb9g3"/>
  <title>Migration from FRA1 to FRA2</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 8 hours</p>
    <p><strong>Affected Components:</strong> DNS Server, Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A maintenance will be performed on the weekend.

### WHEN?

On May 24, 2025, starting at 4:00 AM (CEST), we will migrate our infrastructure from FRA1 to our new FRA2 facility, which became operational in January of this year.   

The maintenance is expected to last until 10:00 AM (CEST) due to the complex nature of the tasks involved.

### WHY?

This migration is part of our ongoing commitment to improve our services and facilities.   

Several months ago, we experienced two brief power-related outages affecting FRA1, which were beyond our control. 

These incidents, among other factors, prompted us to reassess long-term risks and make necessary adjustments.

The new FRA2 facility offers improved availability, 24/7 on-site support, and is built on our fully redundant core routing and switching infrastructure, including DDoS protection.

During the maintenance window, we will be performing the following tasks:

* Migration of physical servers to the new FRA2 region
* Updates to our core virtualization layer
* Integration into our new virtualization cluster
* Migration to our upgraded routing and switching stack

### DETAILS

Please take note of the following important information:

* After completion, all nodes will automatically reboot.
* There will be no changes to your assigned IP addresses or rDNS/PTR entries.
* Our support team will be available throughout the maintenance period to assist you with any questions or concerns.
* The migration will only affect nodes located within the FRA1 region; AMS1, FRA2, and SPO1 will remain online and unaffected.

### SUPPORT

If you have any questions or concerns, please do not hesitate to contact us at [support@v6node.com](mailto:support@v6node.com) or by creating a support ticket.

### Timezones

To help you plan accordingly, here’s the maintenance window in various local times:

\- **New York (EDT)**: 23 May, from 22:00 to 04:00 (next day)

\- **San Francisco (PDT)**: 23 May, from 19:00 to 01:00 (next day)

\- **UTC**: 24 May, from 02:00 to 08:00

\- **London (BST)**: 24 May, from 03:00 to 09:00

\- **Tokyo (JST)**: 24 May, from 11:00 to 17:00

\- **Sydney (AEST)**: 24 May, from 12:00 to 18:00

\- **Dubai (GST)**: 24 May, from 06:00 to 12:00

\- **Mumbai (IST)**: 24 May, from 07:30 to 13:30

\- **Singapore (SGT)**: 24 May, from 10:00 to 16:00

\- **São Paulo (BRT)**: 23 May, from 23:00 to 05:00 (next day)

We, the v6Node team, would like to take this opportunity to personally thank you for your continued trust and support.

Best regards,

The v6Node Team

Ian, Jay, and Patrick.</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>03:27:01</var> GMT+0</small><br /><strong>Identified</strong> -
  All servers have been shut down and dismantled. The servers are now being physically migrated to our new location FRA2\. .</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>10:04:19</var> GMT+0</small><br /><strong>Completed</strong> -
  As of 10:20 am, all nodes have been restarted, and connectivity has been restored.   
A full status update will be provided shortly.

If you have any questions or concerns in the meantime, please don&#039;t hesitate to contact our support team..</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>04:25:16</var> GMT+0</small><br /><strong>Identified</strong> -
  The servers have arrived in the FRA2 facility..</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The maintenance has started..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/cmb14ph64002jgznbl1uglj4i</id>
  <published>2025-05-23T18:23:08.838+00:00</published>
  <updated>2025-05-23T18:23:08.838+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cmb14ph64002jgznbl1uglj4i"/>
  <title>FRA2, pve1: some nodes are unresponsive.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 28 minutes</p>
    <p><strong>Affected Components:</strong> Virtualization Cluster Frankfurt, DE (FRA2)</p>
    <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>18:23:08</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our monitoring showed some unresponsiveness to a small amount of nodes in our FRA2 location on host &quot;pve1&quot;. We are currently investigating this incident..</p>
<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>19:00:44</var> GMT+0</small><br /><strong>Identified</strong> -
  A failing NVMe device has been identified as the cause of the system hanging in an I/O wait state, which led to a lockup. All affected nodes are currently being migrated to different servers. There won’t be any data loss.

All affected customers will receive an account credit as a compensation for this inconvenience.

  
We will update this status report again when the migration has been finalised..</p>
<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>20:51:34</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved as of 21:31 CET. We will investigate the reason for the failure of the NVMe device after tomorrow&#039;s maintenance window. All customers will be reimbursed with a credit, you will get an information on that by e-mail.  

If you encounter any problems with your node, please contact our support team by e-mail to [support@v6Node.com](mailto:support@v6Node.com).</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/cm4wfiz6o004kebe23f2rnb2r</id>
  <published>2024-12-20T07:28:56.478+00:00</published>
  <updated>2024-12-20T07:28:56.478+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cm4wfiz6o004kebe23f2rnb2r"/>
  <title>Frankfurt1 potential loss of connectivity </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Website , Cloud Portal, Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>07:28:56</var> GMT+0</small><br /><strong>Resolved</strong> -
  Connectivity has been restored, and current indications suggest an issue with the transport backhaul. We’ll continue monitoring the situation and provide further details as soon as possible..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Maintenance/cm4lpot6500014lbf625kz5np</id>
  <published>2024-12-15T05:55:00.000+00:00</published>
  <updated>2024-12-15T05:55:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/maintenance/cm4lpot6500014lbf625kz5np"/>
  <title>[URGENT] Critical Power Maintenance in fra1 Region (Dec 14)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 12 minutes</p>
    <p><strong>Affected Components:</strong> Website , Cloud Portal, Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>05:55:00</var> GMT+0</small><br /><strong>Identified</strong> -
  To address the recent power incident in our fra1 datacenter, an urgent 15-20 minute maintenance window has been scheduled by our datacenter provider on **December 14, 2024 at 22:00 CET**. Unfortunately, both power feeds (A+B) will be unavailable, requiring a complete shutdown of all fra1 infrastructure. The shutdown will affect all power connections in the rack simultaneously, as it is technically not possible to replace the fuses for individual phases one after the other according to the datacenter provider.**Impact**\- Duration: 15-20 minutes - Region: fra1 - Affected Systems: All baremetal servers, public and private cloud in fra1 - Start: Dec 14, 21:55 CET - End: Dec 14, 22:20 CET**No Action Required**We will initiate a controlled shutdown of all fra1 services at 21:55 CET. Services in other regions (mep1, spo1) will not be impacted. We apologize for the short notice and inconvenience. This critical maintenance will prevent future power incidents and ensure long-term stability. Our team is available to assist with any concerns throughout the entire maintenance window. If you have any questions or concerns, please don&#039;t hesitate to reach out to us..</p>
<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>20:58:27</var> GMT+0</small><br /><strong>Identified</strong> -
  The maintenance is in progress.</p>
<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>22:10:00</var> GMT+0</small><br /><strong>Completed</strong> -
  The maintenance has been completed. The total downtime has been around 57 minutes.

Our datacenter proider .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/cm4betnan001qhs9930s9av04</id>
  <published>2024-12-05T14:26:03.838+00:00</published>
  <updated>2024-12-05T14:26:03.838+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cm4betnan001qhs9930s9av04"/>
  <title>Power outage at Frankfurt data centre </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>14:26:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  At around 14:35 CET a power outage has occurred at our data centre in Frankfurt, Germany. Although the racks being powered by two different lines, it failed. While we are booting up all our customers Nodes within the next few minutes, we will investigate further why this has happened. 

Open support requests will be updated throughout the day. All affected customers will be contacted by us within the next few days to discuss this matter and apply compensation for the circumstances experienced. 

The situation is under control and nodes are booting again. 

Thanks for your understanding!.</p>
<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>14:45:52</var> GMT+0</small><br /><strong>Resolved</strong> -
  All nodes are operational again. If you encounter any issues, please send an e-mail to [hi@v6Node.com](mailto:hi@v6Node.com)

Total outage was 70 minutes. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/cm41329d8000a99jjbj0d0rm2</id>
  <published>2024-11-27T23:38:00.000+00:00</published>
  <updated>2024-11-27T23:38:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cm41329d8000a99jjbj0d0rm2"/>
  <title>Fiber Cut Causing Network Instability in US-West (Spokane)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> Virtualization Cluster Spokane, US</p>
    <p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>23:38:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Due to a fiber cut, we are experiencing intermittent network connectivity issues at our US-West (Spokane) location. The upstream provider has dispatched a team to assess and repair the damage on-site.

Currently, connectivity is being maintained by a backup transit via a separate circuit. However, due to congestion, some networks are still experiencing disruptions..</p>
<p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/cm3uqu0oi000437uk5cwjio37</id>
  <published>2024-11-23T22:15:00.000+00:00</published>
  <updated>2024-11-23T22:15:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cm3uqu0oi000437uk5cwjio37"/>
  <title>Routing problems, degraded performance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> Cloud Portal, Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>22:15:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We currently experience a outage in our edge routing, and investigating the situation.

Our transit has been rerouted through another BGP transit provider.

See: &lt;https://status.dataforest.net/incidents/f0rgydm971v9&gt;.</p>
<p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>22:45:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The situation is under control and we are monitoring the transit routes. No degradation is expected..</p>
<p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/clw695mh155088biljydygec76</id>
  <published>2024-05-14T10:30:54.024+00:00</published>
  <updated>2024-05-14T10:30:54.024+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/clw695mh155088biljydygec76"/>
  <title>Loss of Connectivity in MK Netzdienste FRA2</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> Website , Cloud Portal, Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>10:30:54</var> GMT+0</small><br /><strong>Identified</strong> -
  We are experiencing connectivity issues due to a power outage at InterXion FRA2\. This affects multiple providers connected to our FRA2 presence, both locally and through transport.  
 Our team is working closely with suppliers to restore service as soon as possible.   
  
Thank you for your patience..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>11:16:50</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have implemented a fix by routing traffic over an alternative link and backhauling internet connectivity from our PoP in Meppel, NL. We are currently closely monitoring the situation..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>13:45:13</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The first of our fibre paths connecting our infrastructure in Frankfurt has been restored, connectivity is performing as normal now. We continue to watch the situation as it evolves..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Ever since May 14th 17:00 (Berlin time), all connectivity has been restored. 

Post mortem is to follow. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/clo5zagjc11947b4or1xxxn4k0</id>
  <published>2023-10-25T15:50:00.000+00:00</published>
  <updated>2023-10-25T15:50:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/clo5zagjc11947b4or1xxxn4k0"/>
  <title>Network issues in Frankfurt</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Website , Cloud Portal, DNS Server, Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>15:50:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We would like to inform you that one of our upstream providers recently encountered some technical challenges. Under normal circumstances, our backup transit provider would have ensured uninterrupted service. However, due to an earlier issue where legitimate traffic was mistakenly flagged as a DDoS attack by their anti-DDoS solution, this backup was temporarily disabled.

We deeply regret any inconvenience caused and assure you that we are taking measures to enhance our network robustness. We are in the process of onboarding two additional transit providers by year&#039;s end. This will not only expand our overall network capacity but also diversify our network blend, further minimizing potential disruptions in the future.

Thank you for your patience and understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Incident/cllfjvkod38206ayo7rf6bwn5m</id>
  <published>2023-08-17T18:20:00.000+00:00</published>
  <updated>2023-08-17T18:20:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/incident/cllfjvkod38206ayo7rf6bwn5m"/>
  <title>Temporary Connectivity Interruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>18:20:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our monitoring systems have detected a partial loss of connectivity between 20:20 CEST and 20:30 CEST. We are actively monitoring the situation and will temporarily disable our sessions with a transit provider that appears to be contributing to this issue.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Maintenance/clj5m5npf575979b0oiwt0y4mfw</id>
  <published>2023-06-21T13:30:00.000+00:00</published>
  <updated>2023-06-21T13:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/maintenance/clj5m5npf575979b0oiwt0y4mfw"/>
  <title>Scheduled Kernel Update and Reboot</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A necessary kernel update will be performed today at 15:30 UTC+2, requiring a host reboot. The anticipated downtime is approximately 10 minutes. 
Only Nodes located on pve1 are affected..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>13:49:55</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.v6node.com,2005:Maintenance/cli378jls27221b0n49qo6wvwk</id>
  <published>2023-05-26T13:00:00.000+00:00</published>
  <updated>2023-05-26T13:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.v6node.com/maintenance/cli378jls27221b0n49qo6wvwk"/>
  <title>Datacenter migration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> Website , Cloud Portal, DNS Server, Virtualization Cluster Frankfurt, DE (FRA1)</p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We would like to inform you about an upcoming maintenance event where we will be migrating our infrastructure to our primary location with MK Netzdienste. This move will provide a more energy-efficient and eco-friendly datacenter in Frankfurt. We will also be adding CDN77 and Meerfarbig to our upstream blend and upgrading our networking setup for future enhancements. The maintenance will occur on Friday, May 26th, during specific timeframes mentioned in the email. Our Cloud Panel and Frankfurt-hosted Nodes will be temporarily unavailable during this period. For further updates, please visit our status page at http://status.v6node.com. We apologize for any inconvenience caused and are available to address any concerns you may have..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  All servers have arrived in our new datacenter location and are currently being racked and powered up again by our service staff..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>15:33:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance will be extended until 07:00 pm as we are still making optimizations to the network infrastructure. We will inform you when the maintenance is finished and all services are available again..</p>

        ]]>
  </content>
</entry>

</feed>