<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Webdock Status - Incident history</title>
    <link>https://status.webdock.io</link>
    <description>Webdock</description>
    <pubDate>Wed, 20 May 2026 08:00:00 +0000</pubDate>
    
<item>
  <title>Network maintenance in DK DC1</title>
  <description>
    Type: Maintenance
    

    Affected Components: Denmark: Network Infrastructure
    May 20, 08:00:00 GMT+0 - Identified - We will be performing important security enhancements to our network on Wednesday the 20th betwen 10.00 and 14.00 CEST. The upgrade procedure includes a full kernel upgrade of all host systems. The procedure WILL result in brief network outage for ALL customers in Denmark. Typically we are looking at 5 seconds of interruption as systems are reloaded, but for some very busy systems or where networking hangs on some customer instance, the duration can be up to a few minutes. We apologize in advance for any inconvenience caused. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing important security enhancements to our network on Wednesday the 20th betwen 10.00 and 14.00 CEST. The upgrade procedure includes a full kernel upgrade of all host systems. The procedure WILL result in brief network outage for ALL customers in Denmark. Typically we are looking at 5 seconds of interruption as systems are reloaded, but for some very busy systems or where networking hangs on some customer instance, the duration can be up to a few minutes. We apologize in advance for any inconvenience caused..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 20 May 2026 08:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmp40h9fk036rp9n14uzgnual</link>
  <guid>https://status.webdock.io/maintenance/cmp40h9fk036rp9n14uzgnual</guid>
</item>

<item>
  <title>Backup cluster degraded</title>
  <description>
    Type: Incident
    Duration: 2 days, 11 hours and 6 minutes

    Affected Components: Denmark: Storage Backend
    May 16, 17:22:33 GMT+0 - Resolved - This incident has been resolved and our backup cluster has been operating nominally for the last 24 hours. May 14, 15:12:35 GMT+0 - Monitoring - We implemented a temporary fix which seems to have elminated the context deadline exceeded errors we were seeing. The underlying issue is still present and pending investigation by the Incus team - what we did was just a &quot;patch&quot; which is fine for now. We will update once we know more. May 14, 06:16:46 GMT+0 - Identified - After a major software upgrade of our backup cluster yesterday we are seeing frequent timeouts while doing backups. This is due to some regression in Incus, our hypervisor. We have the Incus team investigating this and we hope to have this solved within a day or two at most. In the interim, if you get an error trying to perform a snapshot you can retry and hopefully it goes through. Repeated failures however means that your snapshot is indeed present locally, it just isn&#039;t synched out to our storage backend, and it won&#039;t be synched until the underlying issue is solved. This issue seems to mostly affect new instances - &quot;old&quot; instances created before yesterday are not as affected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 11 hours and 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:22:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved and our backup cluster has been operating nominally for the last 24 hours..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:12:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a temporary fix which seems to have elminated the context deadline exceeded errors we were seeing. The underlying issue is still present and pending investigation by the Incus team - what we did was just a &quot;patch&quot; which is fine for now. We will update once we know more..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:16:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  After a major software upgrade of our backup cluster yesterday we are seeing frequent timeouts while doing backups. This is due to some regression in Incus, our hypervisor. We have the Incus team investigating this and we hope to have this solved within a day or two at most. In the interim, if you get an error trying to perform a snapshot you can retry and hopefully it goes through. Repeated failures however means that your snapshot is indeed present locally, it just isn&#039;t synched out to our storage backend, and it won&#039;t be synched until the underlying issue is solved. This issue seems to mostly affect new instances - &quot;old&quot; instances created before yesterday are not as affected..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 14 May 2026 06:16:46 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmp53imce00ahqjjtauon0e6w</link>
  <guid>https://status.webdock.io/incident/cmp53imce00ahqjjtauon0e6w</guid>
</item>

<item>
  <title>Storage backend maintenance in DK DC1</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Denmark: Storage Backend
    May 13, 15:00:00 GMT+0 - Identified - We are expanding our backup storage with another 200TB of storage. The storage backend will be unavailable for 1-2 hours. May 13, 15:00:01 GMT+0 - Identified - Maintenance is now in progress May 13, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are expanding our backup storage with another 200TB of storage. The storage backend will be unavailable for 1-2 hours..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 13 May 2026 15:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmp46gp9q0079p0u1fyu22ilr</link>
  <guid>https://status.webdock.io/maintenance/cmp46gp9q0079p0u1fyu22ilr</guid>
</item>

<item>
  <title>Issue with a single host (lxd-based)</title>
  <description>
    Type: Incident
    Duration: 9 minutes

    Affected Components: Denmark: General Infrastructure
    May 9, 09:21:08 GMT+0 - Investigating - The system hung and needs a reboot. Sorry for the inconvenience. May 9, 09:30:28 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:21:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  The system hung and needs a reboot. Sorry for the inconvenience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:30:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 9 May 2026 09:21:08 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmoy4wgcu06o5bxcpwztzd0w0</link>
  <guid>https://status.webdock.io/incident/cmoy4wgcu06o5bxcpwztzd0w0</guid>
</item>

<item>
  <title>Dashboard will go down briefly</title>
  <description>
    Type: Incident
    Duration: 19 minutes

    Affected Components: Webdock Dashboard, Webdock REST API
    May 6, 12:19:21 GMT+0 - Identified - Due to an upgrade of key systems, we hit an issue affecting legacy container instances. This has had some knock-on effects which is forcing us to reboot the host running the main webdock dashboard. Please expect the dashboard to go down for 5-10 minutes soon. May 6, 12:38:33 GMT+0 - Resolved - Dashboard and related services are up and OK. We apologize for the brief outage. We are continuing work on legacy container instances, but the vast majority of our customers will see no interruption here. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:19:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Due to an upgrade of key systems, we hit an issue affecting legacy container instances. This has had some knock-on effects which is forcing us to reboot the host running the main webdock dashboard. Please expect the dashboard to go down for 5-10 minutes soon..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:38:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Dashboard and related services are up and OK. We apologize for the brief outage. We are continuing work on legacy container instances, but the vast majority of our customers will see no interruption here..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 6 May 2026 12:19:21 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmou0xqw202m52ouciidoaryg</link>
  <guid>https://status.webdock.io/incident/cmou0xqw202m52ouciidoaryg</guid>
</item>

<item>
  <title>A system upgrade is causing issues with legacy hosts.</title>
  <description>
    Type: Incident
    Duration: 3 hours and 59 minutes

    Affected Components: Denmark: General Infrastructure
    May 6, 15:38:53 GMT+0 - Resolved - We rolled out a fix for this. Some of the Xenial instances had trouble getting up as they are using the legacy cgroup. We have put these on a old host that supports cgroup v1\. 

Now everything should work as usual. 

Apologies for the inconvenience caused. May 6, 11:40:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 6, 12:30:00 GMT+0 - Identified - Fix is being rolled out. Restarts will occur on affected servers. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:38:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We rolled out a fix for this. Some of the Xenial instances had trouble getting up as they are using the legacy cgroup. We have put these on a old host that supports cgroup v1\. 

Now everything should work as usual. 

Apologies for the inconvenience caused..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Fix is being rolled out. Restarts will occur on affected servers..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 6 May 2026 11:40:00 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmotzu3ad068821p4inmeswb5</link>
  <guid>https://status.webdock.io/incident/cmotzu3ad068821p4inmeswb5</guid>
</item>

<item>
  <title>Power maintenance in DK DC-1: No impact expected</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Denmark: General Infrastructure
    May 6, 06:30:00 GMT+0 - Identified - The danish utility service needs to do some electric cable splicing near our DC today. They will be cutting power to our facility for up to 3 hours between 8.30 and 11.30 CEST. We expect no impact to our operations or customers, as our emergency power systems should work nominally, just like they have in the recent power maintenance a couple of weeks ago. For this reason we expect no disruption of customer workloads. May 6, 06:30:01 GMT+0 - Identified - Maintenance is now in progress May 6, 09:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The danish utility service needs to do some electric cable splicing near our DC today. They will be cutting power to our facility for up to 3 hours between 8.30 and 11.30 CEST. We expect no impact to our operations or customers, as our emergency power systems should work nominally, just like they have in the recent power maintenance a couple of weeks ago. For this reason we expect no disruption of customer workloads..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 6 May 2026 06:30:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmotnolrs09gxl0b24k9nez7m</link>
  <guid>https://status.webdock.io/maintenance/cmotnolrs09gxl0b24k9nez7m</guid>
</item>

<item>
  <title>Issue with a legacy lxd host</title>
  <description>
    Type: Incident
    Duration: 12 minutes

    Affected Components: Denmark: General Infrastructure
    May 4, 13:07:03 GMT+0 - Identified - The kernel has hung in one of our old legacy host that runs the containers. The host needs a reboot, hence downtime of 5-10 minutes. May 4, 13:19:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:07:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The kernel has hung in one of our old legacy host that runs the containers. The host needs a reboot, hence downtime of 5-10 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:19:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 4 May 2026 13:07:03 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmor7rqul0235qo89iz3c7oiv</link>
  <guid>https://status.webdock.io/incident/cmor7rqul0235qo89iz3c7oiv</guid>
</item>

<item>
  <title>Issue with single host in dk dc1</title>
  <description>
    Type: Incident
    Duration: 29 minutes

    Affected Components: Denmark: General Infrastructure
    May 2, 05:58:24 GMT+0 - Identified - We have a machine down in Denmark. After reboot the system does not have an uplink on its fiber connections anymore and we are investigating why. This system recently received a full kernel upgrade, which may be the reason for the malfunction. May 2, 06:27:37 GMT+0 - Resolved - This incident has been resolved. Sorry for the inconvenience caused 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 29 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:58:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have a machine down in Denmark. After reboot the system does not have an uplink on its fiber connections anymore and we are investigating why. This system recently received a full kernel upgrade, which may be the reason for the malfunction..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:27:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. Sorry for the inconvenience caused.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 2 May 2026 05:58:24 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmonxkqro03wlz0ny8lyooxr1</link>
  <guid>https://status.webdock.io/incident/cmonxkqro03wlz0ny8lyooxr1</guid>
</item>

<item>
  <title>Issue with a single host</title>
  <description>
    Type: Incident
    Duration: 23 minutes

    Affected Components: Denmark: General Infrastructure
    Apr 30, 04:48:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 30, 05:11:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:48:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:11:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 30 Apr 2026 04:48:00 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmol1ldxh052l113oxaftalnv</link>
  <guid>https://status.webdock.io/incident/cmol1ldxh052l113oxaftalnv</guid>
</item>

<item>
  <title>Investigating Temperature Anomaly</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Denmark: General Infrastructure
    Apr 30, 04:00:00 GMT+0 - Identified - A single Ryzen system in our DK DC has a temperature anomaly. We believe one or more fans may have failed in the system and this needs to be investigated. We are reserving 2 hours for this maintenance on thursday morning at 06.00 CEST, just in case, but we expect this to take 45 minutes or less. Your server will go down during this time, and you have been notified by email if you are affected. Apr 30, 04:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 30, 06:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  A single Ryzen system in our DK DC has a temperature anomaly. We believe one or more fans may have failed in the system and this needs to be investigated. We are reserving 2 hours for this maintenance on thursday morning at 06.00 CEST, just in case, but we expect this to take 45 minutes or less. Your server will go down during this time, and you have been notified by email if you are affected..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 30 Apr 2026 04:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmoh93ai01dll6yiynmtva47r</link>
  <guid>https://status.webdock.io/maintenance/cmoh93ai01dll6yiynmtva47r</guid>
</item>

<item>
  <title>Network</title>
  <description>
    Type: Incident
    Duration: 1 hour and 7 minutes

    Affected Components: Denmark: Network Infrastructure
    Apr 29, 11:38:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 29, 11:56:00 GMT+0 - Identified - A routing issue was discovered related to our Voxility configuration. Apr 29, 12:05:00 GMT+0 - Monitoring - Issue has been fixed, monitoring. Apr 29, 12:45:00 GMT+0 - Resolved - Incident has been resolved and improvements are being made to prevent this from happening again 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 7 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:38:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:56:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  A routing issue was discovered related to our Voxility configuration..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Issue has been fixed, monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Incident has been resolved and improvements are being made to prevent this from happening again.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 29 Apr 2026 11:38:00 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmok2f8wy03iiuqnnl89t4qa1</link>
  <guid>https://status.webdock.io/incident/cmok2f8wy03iiuqnnl89t4qa1</guid>
</item>

<item>
  <title>Major Dashboard Upgrade</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Webdock Dashboard
    Apr 27, 18:00:00 GMT+0 - Identified - Monday April 27th at 20.00 CEST we will be performing major upgrades to the Webdock Dashboard at [app.webdock.io](http://app.webdock.io) \- the maintenance will take at most 2 hours, but we hope to complete it in 30 minutes or less. The upgrade requires us to take down the dashboard completely and in this time period you will be unable to use our dashboard to interact with your server, so please make sure you have completed any tasks like server snapshotting or restoring before this time. Your server(s) and all other services will be fully operational, it is only the main dashboard which will go down for maintenance. During the maintenance metrics collection will be paused so you will see a gap in data for utilization metrics for this period of time. No other impact is expected. Apr 27, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 27, 18:23:06 GMT+0 - Identified - The maintenance was quicker than expected, due to us having extensively prepared and tested the procedure beforehand. We are pretty much done, but will be checking logs and other bits and pieces for a little while to make sure everything is running smoothly, before giving the all clear. Apr 27, 18:48:49 GMT+0 - Identified - We found a small issue in our API layer which was fixed a few minutes ago. The API is now fully operational again. We found a small issue in our automated jobs also, which we just fixed. We are continuing to monitor all systems and will update here once we feel we are in a perfect state. Apr 27, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully Apr 27, 20:19:47 GMT+0 - Completed - Maintenance has completed successfully. We have solved a number of minor issues, lastly it was Github login which no longer worked. We should be in a good state now. Enjoy and thanks for your patience with us this evening! :) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Monday April 27th at 20.00 CEST we will be performing major upgrades to the Webdock Dashboard at [app.webdock.io](http://app.webdock.io) \- the maintenance will take at most 2 hours, but we hope to complete it in 30 minutes or less. The upgrade requires us to take down the dashboard completely and in this time period you will be unable to use our dashboard to interact with your server, so please make sure you have completed any tasks like server snapshotting or restoring before this time. Your server(s) and all other services will be fully operational, it is only the main dashboard which will go down for maintenance. During the maintenance metrics collection will be paused so you will see a gap in data for utilization metrics for this period of time. No other impact is expected..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:23:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The maintenance was quicker than expected, due to us having extensively prepared and tested the procedure beforehand. We are pretty much done, but will be checking logs and other bits and pieces for a little while to make sure everything is running smoothly, before giving the all clear..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:48:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We found a small issue in our API layer which was fixed a few minutes ago. The API is now fully operational again. We found a small issue in our automated jobs also, which we just fixed. We are continuing to monitor all systems and will update here once we feel we are in a perfect state..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:19:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully. We have solved a number of minor issues, lastly it was Github login which no longer worked. We should be in a good state now. Enjoy and thanks for your patience with us this evening! :).&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 27 Apr 2026 18:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmoa1b5s5001012tuu6yexfca</link>
  <guid>https://status.webdock.io/maintenance/cmoa1b5s5001012tuu6yexfca</guid>
</item>

<item>
  <title>Issue with lxd host</title>
  <description>
    Type: Incident
    Duration: 21 minutes

    Affected Components: Denmark: General Infrastructure
    Apr 24, 20:46:10 GMT+0 - Investigating - We are currently investigating this incident. Apr 24, 20:46:25 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 24, 21:07:05 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:46:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:46:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:07:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 24 Apr 2026 20:46:10 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmoddrn1h01x9xzv81iocm8ba</link>
  <guid>https://status.webdock.io/incident/cmoddrn1h01x9xzv81iocm8ba</guid>
</item>

<item>
  <title>Power upgrade at DK-DC1</title>
  <description>
    Type: Maintenance
    Duration: 10 hours and 20 minutes

    Affected Components: Denmark: General Infrastructure
    Apr 22, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 22, 05:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance of our power infrastructure on Wednesday April 22nd. In connection with this we will experience a power outage during two seperate windows, the first at 07:00 to 07:40 CEST and the second from 15:00 to 15:40 CEST. We have tested all of our emergency power equipment and we fully expect our UPS and Generator systems to take over during the planned power outage. We do not expect any disruption to our customers. Apr 22, 12:36:31 GMT+0 - Identified - The first power outage happened this morning, a bit later than scheduled but without any impact to our services or customers as was expected. The second planned power outage will start within the next hour or so, and once that completes the maintenance is done. Since everything worked nominally this morning, we do not expect any issues with this second outage today. We will update here once the maintenance is completed. Apr 22, 15:19:35 GMT+0 - Completed - Maintenance has completed successfully and without incident. Webdock is now one step closer to our next big expansion in our DK DC1. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance of our power infrastructure on Wednesday April 22nd. In connection with this we will experience a power outage during two seperate windows, the first at 07:00 to 07:40 CEST and the second from 15:00 to 15:40 CEST. We have tested all of our emergency power equipment and we fully expect our UPS and Generator systems to take over during the planned power outage. We do not expect any disruption to our customers..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:36:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The first power outage happened this morning, a bit later than scheduled but without any impact to our services or customers as was expected. The second planned power outage will start within the next hour or so, and once that completes the maintenance is done. Since everything worked nominally this morning, we do not expect any issues with this second outage today. We will update here once the maintenance is completed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:19:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully and without incident. Webdock is now one step closer to our next big expansion in our DK DC1..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 22 Apr 2026 05:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmo76u4wb0opcwm930hw91xep</link>
  <guid>https://status.webdock.io/maintenance/cmo76u4wb0opcwm930hw91xep</guid>
</item>

<item>
  <title>Kernel and ZFS Upgrade on a Host</title>
  <description>
    Type: Incident
    Duration: 54 minutes

    Affected Components: Denmark: General Infrastructure
    Apr 9, 12:46:01 GMT+0 - Investigating - One host is being unstable and needs a kernel and ZFS upgrade. There will be few minutes of downtime. Affected servers will see an alert in the dashboard. Apr 9, 13:39:56 GMT+0 - Resolved - Maintenance complete. Hopefully no more issues. 

Thanks for your patience and understanding. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 54 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:46:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  One host is being unstable and needs a kernel and ZFS upgrade. There will be few minutes of downtime. Affected servers will see an alert in the dashboard..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:39:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Maintenance complete. Hopefully no more issues. 

Thanks for your patience and understanding..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 9 Apr 2026 12:46:01 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmnrh0dp5018vc69wyitrp5hp</link>
  <guid>https://status.webdock.io/incident/cmnrh0dp5018vc69wyitrp5hp</guid>
</item>

<item>
  <title>Issue with a Ryzen host</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: Denmark: General Infrastructure
    Apr 9, 12:04:11 GMT+0 - Identified - One of our Ryzen hosts has gone offline. Our NOC guys are investigating this. Apr 9, 12:09:57 GMT+0 - Resolved - This incident has been resolved. Sorry for the inconvenience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:04:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  One of our Ryzen hosts has gone offline. Our NOC guys are investigating this..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:09:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. Sorry for the inconvenience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 9 Apr 2026 12:04:11 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmnrfilbp0cgc6xsgvfw4rsx4</link>
  <guid>https://status.webdock.io/incident/cmnrfilbp0cgc6xsgvfw4rsx4</guid>
</item>

<item>
  <title>Issue with a single host (lxd-based)</title>
  <description>
    Type: Incident
    Duration: 11 minutes

    Affected Components: Denmark: General Infrastructure
    Apr 9, 08:45:46 GMT+0 - Identified - We are continuing to work on a fix for this incident. A host reboot might be necessary.

Apologies for the inconvenience. Apr 9, 08:56:33 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:45:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident. A host reboot might be necessary.

Apologies for the inconvenience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:56:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 9 Apr 2026 08:45:46 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmnr8ff2c0b066xsg46swlwxy</link>
  <guid>https://status.webdock.io/incident/cmnr8ff2c0b066xsg46swlwxy</guid>
</item>

<item>
  <title>Single Host Reboot</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Denmark: Network Infrastructure
    Mar 28, 18:34:52 GMT+0 - Resolved - This incident has been resolved. Mar 28, 18:25:02 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:34:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:25:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 28 Mar 2026 18:25:02 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmnanu51v005tdwdr7emlpz2v</link>
  <guid>https://status.webdock.io/incident/cmnanu51v005tdwdr7emlpz2v</guid>
</item>

<item>
  <title>Single Host Reboot</title>
  <description>
    Type: Incident
    Duration: 8 hours and 3 minutes

    Affected Components: Denmark: Network Infrastructure
    Mar 23, 14:24:32 GMT+0 - Investigating - We are currently investigating this incident. Mar 23, 14:32:35 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:24:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:32:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 14:24:32 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmn3a1lg112ur4iurf7sbh3g3</link>
  <guid>https://status.webdock.io/incident/cmn3a1lg112ur4iurf7sbh3g3</guid>
</item>

<item>
  <title>Storage Backend in DK-DC1 under maintenance.</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 23 minutes

    Affected Components: Denmark: Storage Backend
    Mar 12, 19:00:00 GMT+0 - Identified - We are performing some needed maintenance in storage cluster DK DC1 now and for up to 2 hours. In this period, snapshot functionality will not be available. Mar 12, 20:23:08 GMT+0 - Completed - Maintenance has completed successfully. All snapshots operations once again available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing some needed maintenance in storage cluster DK DC1 now and for up to 2 hours. In this period, snapshot functionality will not be available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:23:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully. All snapshots operations once again available..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 12 Mar 2026 19:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmmnuoeip07xcw6ss3r28qjqg</link>
  <guid>https://status.webdock.io/maintenance/cmmnuoeip07xcw6ss3r28qjqg</guid>
</item>

<item>
  <title>A single host needs a reboot</title>
  <description>
    Type: Incident
    Duration: 1 hour and 4 minutes

    Affected Components: Denmark: General Infrastructure
    Mar 6, 03:21:37 GMT+0 - Investigating - One of the hosts (lxd based legacy host) seems unresponsive or crashed. This one needs a reboot. Mar 6, 04:26:01 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:21:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  One of the hosts (lxd based legacy host) seems unresponsive or crashed. This one needs a reboot..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:26:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 6 Mar 2026 03:21:37 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmmebvlw700y9i99hfmu0lw5s</link>
  <guid>https://status.webdock.io/incident/cmmebvlw700y9i99hfmu0lw5s</guid>
</item>

<item>
  <title>A single host needs a reboot</title>
  <description>
    Type: Incident
    Duration: 16 minutes

    Affected Components: Denmark: General Infrastructure
    Mar 5, 03:16:29 GMT+0 - Investigating - One of the hosts (lxd based legacy host) seems unresponsive or crashed. This one needs a reboot. Mar 5, 03:32:33 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:16:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  One of the hosts (lxd based legacy host) seems unresponsive or crashed. This one needs a reboot..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:32:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 5 Mar 2026 03:16:29 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmmcw953l0w5z50p1jh9s4h22</link>
  <guid>https://status.webdock.io/incident/cmmcw953l0w5z50p1jh9s4h22</guid>
</item>

<item>
  <title>A single host needs a reboot</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: Denmark: General Infrastructure
    Mar 4, 12:35:33 GMT+0 - Investigating - One of the hosts (lxd based legacy host) seems unresponsive or crashed. This one needs a reboot. Mar 4, 12:41:20 GMT+0 - Resolved - This incident has been resolved. Sorry for the inconvenience caused. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:35:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  One of the hosts (lxd based legacy host) seems unresponsive or crashed. This one needs a reboot..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:41:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. Sorry for the inconvenience caused..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 4 Mar 2026 12:35:33 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmmc0s9m100wlro8jszakrg93</link>
  <guid>https://status.webdock.io/incident/cmmc0s9m100wlro8jszakrg93</guid>
</item>

<item>
  <title>Issue with another host (lxd-based)</title>
  <description>
    Type: Incident
    Duration: 14 minutes

    Affected Components: Denmark: General Infrastructure
    Mar 2, 14:08:30 GMT+0 - Identified - This one as well needs a reboot. Apologies for the inconvenience. Mar 2, 14:22:09 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:08:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  This one as well needs a reboot. Apologies for the inconvenience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:22:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Mar 2026 14:08:30 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmm99834d05lsocckac7nzk8u</link>
  <guid>https://status.webdock.io/incident/cmm99834d05lsocckac7nzk8u</guid>
</item>

<item>
  <title>Network issue in Denmark</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: Denmark: Network Infrastructure
    Mar 2, 12:49:19 GMT+0 - Investigating - Some ip ranges are not being routed correctly with BGP at the moment. This seems to be related to a fault in Frankfurt where some network device went down. We are currently investigating this incident. Mar 2, 12:55:06 GMT+0 - Resolved - This incident has been resolved. It was caused by a DC tech pulling a power cable in Frankfurt they shouldn&#039;t have. The device needed to boot and rebuild routing tables - the impact was only parts of our IP space and for about \~10 minutes.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:49:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Some ip ranges are not being routed correctly with BGP at the moment. This seems to be related to a fault in Frankfurt where some network device went down. We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:55:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. It was caused by a DC tech pulling a power cable in Frankfurt they shouldn&#039;t have. The device needed to boot and rebuild routing tables - the impact was only parts of our IP space and for about \~10 minutes. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Mar 2026 12:49:19 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmm96e5ft04zkocckzv7k1h1n</link>
  <guid>https://status.webdock.io/incident/cmm96e5ft04zkocckzv7k1h1n</guid>
</item>

<item>
  <title>A single host needs a reboot</title>
  <description>
    Type: Incident
    Duration: 7 minutes

    Affected Components: Denmark: General Infrastructure
    Mar 2, 09:56:00 GMT+0 - Identified - The host needs a reboot. Instances will be again reachable in 5-10 minutes. Apologies for any inconvenience caused. Mar 2, 10:02:31 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:56:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The host needs a reboot. Instances will be again reachable in 5-10 minutes. Apologies for any inconvenience caused..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:02:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Mar 2026 09:56:00 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmm907dkl036cvnuvapwy61oz</link>
  <guid>https://status.webdock.io/incident/cmm907dkl036cvnuvapwy61oz</guid>
</item>

<item>
  <title>Problems communicating with Epyc Host</title>
  <description>
    Type: Incident
    Duration: 1 hour and 28 minutes

    Affected Components: Denmark: General Infrastructure
    Feb 25, 00:46:26 GMT+0 - Identified - We are having issues communicating with one of our Epyc hosts - all customers there are running fine, we just have problems interacting with and sending commands to the host system. Feb 25, 01:55:21 GMT+0 - Identified - We have to now escalate this to a downtime scenario as we are completely unable to reach the control plane of this host. The host will need a reboot and some maintenance. This means all customers on this host will now go down for anything up to 2 hours unfortunately, depending on the severity of the issue. We will update once we know more.  Feb 25, 02:14:42 GMT+0 - Resolved - Fortunately the issue was not as critical as feared and all services came up after a reboot. We saw at most 5 minutes of downtime here today. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:46:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are having issues communicating with one of our Epyc hosts - all customers there are running fine, we just have problems interacting with and sending commands to the host system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:55:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have to now escalate this to a downtime scenario as we are completely unable to reach the control plane of this host. The host will need a reboot and some maintenance. This means all customers on this host will now go down for anything up to 2 hours unfortunately, depending on the severity of the issue. We will update once we know more. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:14:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Fortunately the issue was not as critical as feared and all services came up after a reboot. We saw at most 5 minutes of downtime here today. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 25 Feb 2026 00:46:26 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmm1bdc7t03mn9d6c2rm5p7ni</link>
  <guid>https://status.webdock.io/incident/cmm1bdc7t03mn9d6c2rm5p7ni</guid>
</item>

<item>
  <title>Issue with a single host (lxd-based)</title>
  <description>
    Type: Incident
    Duration: 28 minutes

    Affected Components: Denmark: General Infrastructure
    Feb 22, 14:44:53 GMT+0 - Identified - The host needs a reboot for proper functioning. Sorry for the inconvenience Feb 22, 15:12:59 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:44:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The host needs a reboot for proper functioning. Sorry for the inconvenience.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:12:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 22 Feb 2026 14:44:53 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmlxv02bl0aq14exrbt6d6ncg</link>
  <guid>https://status.webdock.io/incident/cmlxv02bl0aq14exrbt6d6ncg</guid>
</item>

<item>
  <title>Issue with lxd host</title>
  <description>
    Type: Incident
    Duration: 16 minutes

    Affected Components: Denmark: General Infrastructure
    Feb 16, 16:56:00 GMT+0 - Investigating - We are currently investigating this incident. Feb 16, 17:12:22 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:56:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:12:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 16 Feb 2026 16:56:00 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmlpf1krk021vm9vlz5o8i9hz</link>
  <guid>https://status.webdock.io/incident/cmlpf1krk021vm9vlz5o8i9hz</guid>
</item>

<item>
  <title>Issue with a single host (lxd-based)</title>
  <description>
    Type: Incident
    Duration: 8 minutes

    Affected Components: Denmark: General Infrastructure
    Feb 10, 09:13:39 GMT+0 - Identified - The host requires a reboot. Instances will face downtime for 2-5 minutes.

Sorry for the inconvenience. Feb 10, 09:21:29 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:13:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The host requires a reboot. Instances will face downtime for 2-5 minutes.

Sorry for the inconvenience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:21:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 10 Feb 2026 09:13:39 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmlgdvvrq000hy4pvgd55emgy</link>
  <guid>https://status.webdock.io/incident/cmlgdvvrq000hy4pvgd55emgy</guid>
</item>

<item>
  <title>Issue with lxd host</title>
  <description>
    Type: Incident
    Duration: 31 minutes

    Affected Components: Denmark: Network Infrastructure
    Jan 20, 16:07:40 GMT+0 - Investigating - We are currently investigating this incident. Jan 20, 16:38:06 GMT+0 - Identified - The issue has been fixed. Jan 20, 16:38:19 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:07:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:38:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been fixed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:38:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 20 Jan 2026 16:07:40 +0000</pubDate>
  <link>https://status.webdock.io/incident/cmkmsffep016dxjngse32op08</link>
  <guid>https://status.webdock.io/incident/cmkmsffep016dxjngse32op08</guid>
</item>

<item>
  <title>Fiber optics and cable replacement </title>
  <description>
    Type: Maintenance
    Duration: 8 minutes

    Affected Components: Denmark: Network Infrastructure
    Oct 11, 17:15:00 GMT+0 - Identified - Our NOC team has identified and issue with a flapping link and high CRC errors rate for the past 2 days. We will attempt to fix the issue by changing optics. Oct 11, 17:15:01 GMT+0 - Identified - Maintenance is now in progress Oct 11, 17:22:54 GMT+0 - Completed - Maintenance has completed successfully. No impact to customer workloads was seen. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our NOC team has identified and issue with a flapping link and high CRC errors rate for the past 2 days. We will attempt to fix the issue by changing optics..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:15:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:22:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully. No impact to customer workloads was seen..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 11 Oct 2025 17:15:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmgmj9z0l0a4z2dweodmb7ccc</link>
  <guid>https://status.webdock.io/maintenance/cmgmj9z0l0a4z2dweodmb7ccc</guid>
</item>

<item>
  <title>Webdock Website and Dashboard maintenance</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Webdock Dashboard, Webdock Website, Webdock REST API
    Oct 2, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 2, 08:00:00 GMT+0 - Identified - Edit this maintenance has been bumped by +1 day from what was originally planned.  
  
We will be splitting our front-end website and docs from our dashboard systems tomorrow during the day, sometime between 10.00 and 13.00 CET. This should cause minimal disruption, but we do expect a couple of minutes of potential web server error messages as SSL Certificates are being generated and DNS is switching over. Oct 2, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Edit this maintenance has been bumped by +1 day from what was originally planned.  
  
We will be splitting our front-end website and docs from our dashboard systems tomorrow during the day, sometime between 10.00 and 13.00 CET. This should cause minimal disruption, but we do expect a couple of minutes of potential web server error messages as SSL Certificates are being generated and DNS is switching over..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 2 Oct 2025 08:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmg6el8kv00xif33oc02ht4re</link>
  <guid>https://status.webdock.io/maintenance/cmg6el8kv00xif33oc02ht4re</guid>
</item>

<item>
  <title>Electric Works in DK-DC1</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Denmark: General Infrastructure
    Sep 25, 06:00:00 GMT+0 - Identified - This thursday morning some electric works will be happening at the DK DC1\. We are getting new power supply added increasing our allowed power draw from the grid. The procedure means that mains power will need to be cut for about 5-10 minutes. This should be handled by our UPS and Generator systems - but just in case something unexpected happens we are announcing this 2 hour maintenance window. Sep 25, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 25, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  This thursday morning some electric works will be happening at the DK DC1\. We are getting new power supply added increasing our allowed power draw from the grid. The procedure means that mains power will need to be cut for about 5-10 minutes. This should be handled by our UPS and Generator systems - but just in case something unexpected happens we are announcing this 2 hour maintenance window..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 25 Sep 2025 06:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmfv04pap00lkxc92tfuxp8a3</link>
  <guid>https://status.webdock.io/maintenance/cmfv04pap00lkxc92tfuxp8a3</guid>
</item>

<item>
  <title>Electric works in DK DC1</title>
  <description>
    Type: Maintenance
    Duration: 1 day, 7 hours and 44 minutes

    Affected Components: Denmark: General Infrastructure
    Jun 27, 07:00:00 GMT+0 - Identified - We are activating new solar power generating capacity in the DK-DC1 today. The electricians do not expect any disruption of power or think that we need to do any sort of emergency power testing today, so no disruption is expected. Jun 27, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Jun 26, 07:15:46 GMT+0 - Identified - Maintenance is now in progress. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day, 7 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are activating new solar power generating capacity in the DK-DC1 today. The electricians do not expect any disruption of power or think that we need to do any sort of emergency power testing today, so no disruption is expected..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:15:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 27 Jun 2025 07:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmcd1sqim002ids0xy6tn22nw</link>
  <guid>https://status.webdock.io/maintenance/cmcd1sqim002ids0xy6tn22nw</guid>
</item>

<item>
  <title>Maintenace Regarding Routing Policy</title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    Affected Components: Denmark: Network Infrastructure
    Jun 20, 10:50:01 GMT+0 - Identified - Maintenance is now in progress Jun 20, 11:05:00 GMT+0 - Completed - Maintenance has completed successfully Jun 20, 10:50:00 GMT+0 - Identified - A 15 minute maintenance to adjust routing policy on core routers. No downtime expected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:50:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  A 15 minute maintenance to adjust routing policy on core routers. No downtime expected..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 20 Jun 2025 10:50:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmc4nsqva00175do6wjuc45tm</link>
  <guid>https://status.webdock.io/maintenance/cmc4nsqva00175do6wjuc45tm</guid>
</item>

<item>
  <title>Short Network Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 23 hours and 42 minutes

    Affected Components: Denmark: Network Infrastructure
    Jun 18, 13:33:10 GMT+0 - Completed - Maintenance has completed successfully. Jun 19, 13:15:00 GMT+0 - Identified - We will adjust bgp policy on Core routers, this will lead to bgp flaps between Core routers and Spine/leaf switches. Traffic disruption is not expected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 23 hours and 42 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:33:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will adjust bgp policy on Core routers, this will lead to bgp flaps between Core routers and Spine/leaf switches. Traffic disruption is not expected..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 19 Jun 2025 13:15:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmc1ym0lx000bttyz7wffhfig</link>
  <guid>https://status.webdock.io/maintenance/cmc1ym0lx000bttyz7wffhfig</guid>
</item>

<item>
  <title>Maintenance on Core Routers</title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    Affected Components: Denmark: Network Infrastructure
    Jun 19, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 19, 13:15:00 GMT+0 - Completed - Maintenance has completed successfully Jun 19, 13:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance to adjust core routers BGP policy. Downtime not expected 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance to adjust core routers BGP policy. Downtime not expected.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 19 Jun 2025 13:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmc3dytfo000km71jscp9vj3m</link>
  <guid>https://status.webdock.io/maintenance/cmc3dytfo000km71jscp9vj3m</guid>
</item>

<item>
  <title>Storage backend maintenance</title>
  <description>
    Type: Maintenance
    Duration: 18 hours and 41 minutes

    Affected Components: Denmark: Storage Backend
    Jun 4, 12:18:43 GMT+0 - Completed - Maintenance has completed successfully. Jun 5, 07:00:00 GMT+0 - Identified - We are doing maintenance work on our backup storage backend today. The work will be ongoing throughout the day and for periods of time you will not be able to interact with snapshots. This work also means that for today some subset of our customers will not receive an automatic system snapshot for today, but these should resume tomorrow as normal. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 18 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:18:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are doing maintenance work on our backup storage backend today. The work will be ongoing throughout the day and for periods of time you will not be able to interact with snapshots. This work also means that for today some subset of our customers will not receive an automatic system snapshot for today, but these should resume tomorrow as normal..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 5 Jun 2025 07:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmbhn4znb0001d5de7bso2k3c</link>
  <guid>https://status.webdock.io/maintenance/cmbhn4znb0001d5de7bso2k3c</guid>
</item>

<item>
  <title>Host needs kernel upgrade and restart</title>
  <description>
    Type: Maintenance
    Duration: 11 minutes

    
    May 5, 07:36:29 GMT+0 - Identified - Maintenance is now in progress. May 5, 07:47:54 GMT+0 - Completed - Maintenance complete and all customers are up May 5, 07:15:44 GMT+0 - Identified - We have a host machine which needs a kernel upgrade and reboot. Your VPS will go down for at most 5-10 minutes, usually a lot less. You can check if your server(s) are affected by logging in to Webdock as this will then be shown at the top of the page in a red alert window. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:36:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:47:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance complete and all customers are up.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:15:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have a host machine which needs a kernel upgrade and reboot. Your VPS will go down for at most 5-10 minutes, usually a lot less. You can check if your server(s) are affected by logging in to Webdock as this will then be shown at the top of the page in a red alert window..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 5 May 2025 07:15:44 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cmaaro85c000j11pm9j0zddxm</link>
  <guid>https://status.webdock.io/maintenance/cmaaro85c000j11pm9j0zddxm</guid>
</item>

<item>
  <title>Host needs kernel upgrade and restart</title>
  <description>
    Type: Maintenance
    Duration: 13 minutes

    Affected Components: Denmark: General Infrastructure
    Apr 30, 16:38:39 GMT+0 - Completed - The reboot has been completed and all customer instances are up. We apologize for the brief downtime. Apr 30, 16:26:01 GMT+0 - Identified - We have a host machine which needs a kernel upgrade and reboot. Your VPS will go down for at most 5-10 minutes, usually a lot less. You can check if your server(s) are affected by logging in to Webdock as this will then be shown at the top of the page in a red alert window. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:38:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The reboot has been completed and all customer instances are up. We apologize for the brief downtime..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:26:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have a host machine which needs a kernel upgrade and reboot. Your VPS will go down for at most 5-10 minutes, usually a lot less. You can check if your server(s) are affected by logging in to Webdock as this will then be shown at the top of the page in a red alert window..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 30 Apr 2025 16:26:01 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cma45ey5e00d8c0crnhoc3o0c</link>
  <guid>https://status.webdock.io/maintenance/cma45ey5e00d8c0crnhoc3o0c</guid>
</item>

<item>
  <title>Fiber rewiring in single rack in DK DC Monday Feb. 17th 16.00-19.00</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Denmark: Network Infrastructure
    Feb 17, 18:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 17, 15:00:00 GMT+0 - Identified - On monday we will be tidying up wiring in a rack in our Denmark DC for better airflow and accessibility. The procedure involves replacing fiber uplinks one by one. As we have a fully redundant and routed infrastructure, if no mistakes are made, then our customers should not notice anything happening during this maintenance window. As there is always a small chance that a mistake happens or a cable gets snagged in which case a brief network outage could happen. For this reason we are announcing this maintenance window. Feb 17, 15:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  On monday we will be tidying up wiring in a rack in our Denmark DC for better airflow and accessibility. The procedure involves replacing fiber uplinks one by one. As we have a fully redundant and routed infrastructure, if no mistakes are made, then our customers should not notice anything happening during this maintenance window. As there is always a small chance that a mistake happens or a cable gets snagged in which case a brief network outage could happen. For this reason we are announcing this maintenance window..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 17 Feb 2025 15:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cm74l6q91007g13m6bmy47e8d</link>
  <guid>https://status.webdock.io/maintenance/cm74l6q91007g13m6bmy47e8d</guid>
</item>

<item>
  <title>Rescheduled: Electrics maintenance for single rack in DK DC1 Thursday January 30th</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 12 minutes

    Affected Components: Denmark: General Infrastructure
    Jan 30, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 30, 07:00:00 GMT+0 - Identified - This maintenance has been rescheduled for Thursday January 30th, due to some required equipment not making it to us in time.   
  
On Thursday we will be performing some electrics related maintenance for the rack which tripped fuses when we did our generator upgrade and power outage tests the other day. The maintenance consists of putting less sensitive fuses on both of our circuits and potentially replacing a power transfer switch. We hope that the work will happen without incident, but there is a chance that power may go away from that rack again - we cannot guarantee this will not happen. This will impact most of our Ryzen workloads, our Epyc workloads and our core services such as our dashboard. If a power incident occurs, we will be operational again within about 5-10 minutes and our entire team will be standing by to make sure everything comes up as quickly as possible after a potential failure.  

We absolutely need to solve this issue as the situation is now, then if we have an unplanned power outage there is a chance this rack will go down, and we don&#039;t want that. In fact, everything we&#039;ve designed in our DC is designed to prevent exactly this. We hope to get this issue resolved fully on thursday and hopefully without incident. Jan 30, 08:11:47 GMT+0 - Completed - The maintenance for today is complete. All customer VPS servers are up and running. Unfortunately we saw another outage in the rack but that helped us diagnose the issue, which was a faulty power transfer switch as we had surmised. The switch has been replaced and thus the issue has been solved. This means that in case of an unplanned power outage, all our emergency power systems in that rack will behave properly. After the initial crash we did repeated tests and everything was nominal for all racks and equipment in the DC.  
  
We apologize for any inconvenience caused here this morning. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  This maintenance has been rescheduled for Thursday January 30th, due to some required equipment not making it to us in time.   
  
On Thursday we will be performing some electrics related maintenance for the rack which tripped fuses when we did our generator upgrade and power outage tests the other day. The maintenance consists of putting less sensitive fuses on both of our circuits and potentially replacing a power transfer switch. We hope that the work will happen without incident, but there is a chance that power may go away from that rack again - we cannot guarantee this will not happen. This will impact most of our Ryzen workloads, our Epyc workloads and our core services such as our dashboard. If a power incident occurs, we will be operational again within about 5-10 minutes and our entire team will be standing by to make sure everything comes up as quickly as possible after a potential failure.  

We absolutely need to solve this issue as the situation is now, then if we have an unplanned power outage there is a chance this rack will go down, and we don&#039;t want that. In fact, everything we&#039;ve designed in our DC is designed to prevent exactly this. We hope to get this issue resolved fully on thursday and hopefully without incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:11:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The maintenance for today is complete. All customer VPS servers are up and running. Unfortunately we saw another outage in the rack but that helped us diagnose the issue, which was a faulty power transfer switch as we had surmised. The switch has been replaced and thus the issue has been solved. This means that in case of an unplanned power outage, all our emergency power systems in that rack will behave properly. After the initial crash we did repeated tests and everything was nominal for all racks and equipment in the DC.  
  
We apologize for any inconvenience caused here this morning..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 30 Jan 2025 07:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cm6g7rssq004txutrgvd07uw2</link>
  <guid>https://status.webdock.io/maintenance/cm6g7rssq004txutrgvd07uw2</guid>
</item>

<item>
  <title>Electrics maintenance for single rack in DK DC1 Tuesday January 28th</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 25 minutes

    Affected Components: Denmark: General Infrastructure
    Jan 28, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 28, 07:00:00 GMT+0 - Identified - On Tuesday January 28th we will be performing some electrics related maintenance for the rack which tripped fuses when we did our generator upgrade and power outage tests the other day. The maintenance consists of putting less sensitive fuses on both of our circuits and potentially replacing a power transfer switch. We hope that the work will happen without incident, but there is a chance that power may go away from that rack again - we cannot guarantee this will not happen. This will impact most of our Ryzen workloads, our Epyc workloads and our core services such as our dashboard. If a power incident occurs, we will be operational again within about 5-10 minutes and our entire team will be standing by to make sure everything comes up as quickly as possible after a potential failure.

We absolutely need to solve this issue as the situation is now, then if we have an unplanned power outage there is a chance this rack will go down, and we don&#039;t want that. In fact, everything we&#039;ve designed in our DC is designed to prevent exactly this. We hope to get this issue resolved fully on tuesday and hopefully without incident. Jan 28, 08:24:47 GMT+0 - Completed - The maintenance has been rescheduled for thursday January 30th 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 25 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  On Tuesday January 28th we will be performing some electrics related maintenance for the rack which tripped fuses when we did our generator upgrade and power outage tests the other day. The maintenance consists of putting less sensitive fuses on both of our circuits and potentially replacing a power transfer switch. We hope that the work will happen without incident, but there is a chance that power may go away from that rack again - we cannot guarantee this will not happen. This will impact most of our Ryzen workloads, our Epyc workloads and our core services such as our dashboard. If a power incident occurs, we will be operational again within about 5-10 minutes and our entire team will be standing by to make sure everything comes up as quickly as possible after a potential failure.

We absolutely need to solve this issue as the situation is now, then if we have an unplanned power outage there is a chance this rack will go down, and we don&#039;t want that. In fact, everything we&#039;ve designed in our DC is designed to prevent exactly this. We hope to get this issue resolved fully on tuesday and hopefully without incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:24:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The maintenance has been rescheduled for thursday January 30th.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 28 Jan 2025 07:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cm695avkr002vhvf8o5xnlqak</link>
  <guid>https://status.webdock.io/maintenance/cm695avkr002vhvf8o5xnlqak</guid>
</item>

<item>
  <title>Network Maintenance in Montreal January 23rd</title>
  <description>
    Type: Maintenance
    Duration: 13 hours and 5 minutes

    
    Jan 22, 23:00:00 GMT+0 - Identified - Maintenance is now in progress Jan 22, 23:00:00 GMT+0 - Identified - Update: this maintenance window has been rescheduled to January 23rd. The new information from our DC provider is as follows:

Time Frame:  
Start Time: 6:00AM EST  
End Time: 8:00AM EST  
Expected Downtime: 30 minutes  
  
As before, we are expecting only a brief loss of network connectivity. Thank you for your patience. Jan 23, 12:05:27 GMT+0 - Completed - The maintenance is complete and we have connectivity again. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 13 hours and 5 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Update: this maintenance window has been rescheduled to January 23rd. The new information from our DC provider is as follows:

Time Frame:  
Start Time: 6:00AM EST  
End Time: 8:00AM EST  
Expected Downtime: 30 minutes  
  
As before, we are expecting only a brief loss of network connectivity. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:05:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The maintenance is complete and we have connectivity again..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 22 Jan 2025 23:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cm5p8cibd004udi8kou2k9emk</link>
  <guid>https://status.webdock.io/maintenance/cm5p8cibd004udi8kou2k9emk</guid>
</item>

<item>
  <title>General Network Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 days

    Affected Components: Denmark: Network Infrastructure
    Jan 21, 08:30:00 GMT+0 - Identified - Today and tomorrow we are doing some general network maintenance. The changes made are to improve our routing within our Denmark DC. The changes should not affect any customer workloads other than a tiny percentage of VPS servers which currently have erroneous configuration. In cases where a VPS is affected, it is only impacted for a few seconds as routing is being reconfigured. The impact should be minimal and likely not noticeable by our customers. If you do experience some sort of network issue that lasts more than a minute or two, please reach out to our support team. Jan 21, 08:30:01 GMT+0 - Identified - Maintenance is now in progress Jan 23, 08:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 days</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Today and tomorrow we are doing some general network maintenance. The changes made are to improve our routing within our Denmark DC. The changes should not affect any customer workloads other than a tiny percentage of VPS servers which currently have erroneous configuration. In cases where a VPS is affected, it is only impacted for a few seconds as routing is being reconfigured. The impact should be minimal and likely not noticeable by our customers. If you do experience some sort of network issue that lasts more than a minute or two, please reach out to our support team..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 21 Jan 2025 08:30:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cm667eox5005ot1rkw93j3013</link>
  <guid>https://status.webdock.io/maintenance/cm667eox5005ot1rkw93j3013</guid>
</item>

<item>
  <title>Generator upgrade in Denmark</title>
  <description>
    Type: Maintenance
    Duration: 5 hours

    Affected Components: Denmark: General Infrastructure
    Jan 16, 12:00:00 GMT+0 - Completed - Maintenance has completed successfully Jan 16, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 16, 07:00:00 GMT+0 - Identified - Our emergency power system in Denmark is getting an upgrade today in the form of a new generator. We do not expect any disruption. The only theoretical scenario where things could go wrong is if we have a mains power outage at the exact same time the generator upgrade is happening and that this power outage has a duration of more than 50 minutes. The odds of this are extremely low and we do not expect any disruption of service today. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our emergency power system in Denmark is getting an upgrade today in the form of a new generator. We do not expect any disruption. The only theoretical scenario where things could go wrong is if we have a mains power outage at the exact same time the generator upgrade is happening and that this power outage has a duration of more than 50 minutes. The odds of this are extremely low and we do not expect any disruption of service today..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 16 Jan 2025 07:00:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cm5yyy5ic003sgrku6i6oecbw</link>
  <guid>https://status.webdock.io/maintenance/cm5yyy5ic003sgrku6i6oecbw</guid>
</item>

<item>
  <title>Host needs kernel upgrade and restart in Canada</title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    
    Dec 20, 09:27:38 GMT+0 - Identified - Maintenance is now in progress. Dec 20, 09:27:16 GMT+0 - Identified - We have a host machine in Canada which needs a kernel upgrade and reboot. Your VPS will go down for at most 5-10 minutes, usually a lot less. You can check if your server(s) are affected by logging in to Webdock as this will then be shown at the top of the page in a red alert window. Dec 20, 09:42:08 GMT+0 - Completed - Maintenance complete and all customer servers operational 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:27:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:27:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have a host machine in Canada which needs a kernel upgrade and reboot. Your VPS will go down for at most 5-10 minutes, usually a lot less. You can check if your server(s) are affected by logging in to Webdock as this will then be shown at the top of the page in a red alert window..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:42:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance complete and all customer servers operational.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 20 Dec 2024 09:27:16 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cm4wjrhlb0069ebe2v1718ojh</link>
  <guid>https://status.webdock.io/maintenance/cm4wjrhlb0069ebe2v1718ojh</guid>
</item>

<item>
  <title>Network Maintenance in Denmark</title>
  <description>
    Type: Maintenance
    Duration: 7 days, 23 hours and 13 minutes

    Affected Components: Denmark: Network Infrastructure
    Dec 2, 13:01:00 GMT+0 - Identified - Maintenance is now in progress. Nov 27, 13:01:00 GMT+0 - Identified - We will be performing a rolling update of network configuration across our entire fleet in Denmark today and tomorrow. This update is to ensure the stability of our network and solve a long-standing issue whereby some customers have experienced sudden loss of connectivity due to routes beind dropped on our hosts. This update will eliminate this long-standing issue.  
  
Unfortunately, a subset of our customer instances need to be touched whereby our team adjust the network configuration inside your instance. This will typically only impact customers who have created servers with us recently - older instances and instances created within the last couple of weeks are unaffected and will not be touched.  
  
The operations usually just mean a reload of network configuration whereby - at worst - you will see a few packets lost and that&#039;s it. Only in rare cases where network configuration was already non-standard or bad beforehand in a customer instance will scenarios come up where you may see some disruption. We expect this to be minimal.  
  
Since this is a large task, we expect this maintenance to last throughout the day today and all day tomorrow, possibly longer depending on progress, in which case we will update here.  
  
Thank you for your patience and understanding. Nov 27, 10:05:20 GMT+0 - Identified - This network maintenance has been on-going in stops and starts for the past week or so. We expect the final changes to be completed within the next 2 days. These changes should have NO impact on your server or workloads. Nov 29, 09:19:24 GMT+0 - Identified - We have been slowly pecking away at this in the safest manner possible, and for that reason only a small portion of our fleet in Denmark has been converted to the new configuration. We have decided to let this portion run until monday before doing the remainder and finally completing this maintenance. As stated before: This maintenance should have no impact on your server whatsoever. Dec 5, 09:18:26 GMT+0 - Completed - After slow methodical work over the past two weeks we have completed all the network changes to our entire fleet in Denmark with no disruption to customers. Everything has been checked, double checked and triple checked :D We are happy to close this maintenance at last. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 days, 23 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:01:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:01:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing a rolling update of network configuration across our entire fleet in Denmark today and tomorrow. This update is to ensure the stability of our network and solve a long-standing issue whereby some customers have experienced sudden loss of connectivity due to routes beind dropped on our hosts. This update will eliminate this long-standing issue.  
  
Unfortunately, a subset of our customer instances need to be touched whereby our team adjust the network configuration inside your instance. This will typically only impact customers who have created servers with us recently - older instances and instances created within the last couple of weeks are unaffected and will not be touched.  
  
The operations usually just mean a reload of network configuration whereby - at worst - you will see a few packets lost and that&#039;s it. Only in rare cases where network configuration was already non-standard or bad beforehand in a customer instance will scenarios come up where you may see some disruption. We expect this to be minimal.  
  
Since this is a large task, we expect this maintenance to last throughout the day today and all day tomorrow, possibly longer depending on progress, in which case we will update here.  
  
Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:05:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  This network maintenance has been on-going in stops and starts for the past week or so. We expect the final changes to be completed within the next 2 days. These changes should have NO impact on your server or workloads..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:19:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have been slowly pecking away at this in the safest manner possible, and for that reason only a small portion of our fleet in Denmark has been converted to the new configuration. We have decided to let this portion run until monday before doing the remainder and finally completing this maintenance. As stated before: This maintenance should have no impact on your server whatsoever..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:18:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  After slow methodical work over the past two weeks we have completed all the network changes to our entire fleet in Denmark with no disruption to customers. Everything has been checked, double checked and triple checked :D We are happy to close this maintenance at last..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Dec 2024 13:01:00 +0000</pubDate>
  <link>https://status.webdock.io/maintenance/cm3pwnu6m0008qo87u4hpta07</link>
  <guid>https://status.webdock.io/maintenance/cm3pwnu6m0008qo87u4hpta07</guid>
</item>

  </channel>
  </rss>