Status Status - Incident history https://vapp.instatus.com Status Tue, 3 Dec 2024 06:05:06 +0000 [S2] IP Router 1 DOWN! Type: Incident Dec 3, 06:05:07 GMT+0 - Investigating - \[S2\] IP Router 1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>06:05:07</var> GMT+0</small><br><strong>Investigating</strong> - \[S2\] IP Router 1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Tue, 3 Dec 2024 06:05:06 +0000 https://vapp.instatus.com/incident/cm4821ov8000zrimk0awwstu9 https://vapp.instatus.com/incident/cm4821ov8000zrimk0awwstu9 [S1] PVE1 DOWN! Type: Incident Affected Components: [S1] PVE1 Oct 20, 14:50:05 GMT+0 - Investigating - \[S1\] PVE1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Affected Components:

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>14:50:05</var> GMT+0</small><br><strong>Investigating</strong> - \[S1\] PVE1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sun, 20 Oct 2024 14:50:05 +0000 https://vapp.instatus.com/incident/cm2hpfcae0080zzg0fgcow4do https://vapp.instatus.com/incident/cm2hpfcae0080zzg0fgcow4do [S1] PVE1 DOWN! Type: Incident Duration: 27 minutes Affected Components: [S1] PVE1 Sep 22, 19:56:05 GMT+0 - Resolved - This incident has been resolved. Sep 22, 19:29:08 GMT+0 - Investigating - \[S1\] PVE1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 27 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>19:56:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>19:29:08</var> GMT+0</small><br><strong>Investigating</strong> - \[S1\] PVE1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sun, 22 Sep 2024 19:29:08 +0000 https://vapp.instatus.com/incident/cm1dz2c4e0013ig3hibt1wfuz https://vapp.instatus.com/incident/cm1dz2c4e0013ig3hibt1wfuz virtualized.app DOWN! Type: Incident Duration: 3 minutes Sep 15, 16:45:00 GMT+0 - Resolved - This incident has been resolved. Sep 15, 16:42:06 GMT+0 - Investigating - virtualized.app cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 3 minutes

<p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>16:45:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>16:42:06</var> GMT+0</small><br><strong>Investigating</strong> - virtualized.app cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sun, 15 Sep 2024 16:42:06 +0000 https://vapp.instatus.com/incident/cm13t0kjw01oaraxpxxhbaet1 https://vapp.instatus.com/incident/cm13t0kjw01oaraxpxxhbaet1 virtualized.app DOWN! Type: Incident Duration: 1 minute Sep 9, 17:20:06 GMT+0 - Investigating - virtualized.app cannot be accessed at the moment. This incident was created by an automated monitoring service. Sep 9, 17:21:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 minute

<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>17:20:06</var> GMT+0</small><br><strong>Investigating</strong> - virtualized.app cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>17:21:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 9 Sep 2024 17:20:06 +0000 https://vapp.instatus.com/incident/cm0v9qbth00adpdpk10a8v590 https://vapp.instatus.com/incident/cm0v9qbth00adpdpk10a8v590 Urgen Security Updates takedown Type: Maintenance Duration: 9 hours and 47 minutes Sep 7, 04:43:00 GMT+0 - Identified - Due to urgent required security updates we need to make on our client area we did make it inaccessible until updates are finished. It will be back during the day. You can always contact us via mail@plotnic.de Sep 7, 04:43:50 GMT+0 - Identified - Maintenance is now in progress. Sep 7, 14:30:36 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 9 hours and 47 minutes

<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>04:43:00</var> GMT+0</small><br><strong>Identified</strong> - Due to urgent required security updates we need to make on our client area we did make it inaccessible until updates are finished. It will be back during the day. You can always contact us via mail@plotnic.de.</p> <p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>04:43:50</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>14:30:36</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Sat, 7 Sep 2024 04:43:00 +0000 https://vapp.instatus.com/maintenance/cm0rntpzt004i124ug0t72w98 https://vapp.instatus.com/maintenance/cm0rntpzt004i124ug0t72w98 [S2] IP Router 1 Restructuring Type: Maintenance Duration: 1 hour and 41 minutes Aug 28, 21:06:32 GMT+0 - Identified - Booting works. A persistent configuration so that the LACP boots reliably after startup is currently still being tested. Aug 28, 21:08:30 GMT+0 - Completed - Maintenance has been successfully completed and all announced changes have been implemented. The LACP configuration now seems to work persistently. Thank you for your understanding. Aug 28, 19:00:00 GMT+0 - Identified - Due to ongoing stability issues with our current environment, the IP router will be completely restructured. With this we want to solve the problems in the long term and revive our old usual quality in terms of uptime. Important changes will therefore be made during the specified period to counteract the downtimes. Changes: \- Reinstallation of the router on Bare Metal Debian without Proxmox (virtual environment) to avoid overhead \- Setup of redundant NIC to minimize the risk of failure We hope for your understanding and would like to improve the uptime for you in the long term massive. Aug 28, 19:28:00 GMT+0 - Identified - We are starting. Aug 28, 20:54:37 GMT+0 - Identified - Due to turbulences with the PXE in LACP mode, there will be a delay in completion. we are actively working on this and will inform you as soon as the maintenance has been successfully completed. Type: Maintenance

Duration: 1 hour and 41 minutes

<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>21:06:32</var> GMT+0</small><br><strong>Identified</strong> - Booting works. A persistent configuration so that the LACP boots reliably after startup is currently still being tested..</p> <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>21:08:30</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has been successfully completed and all announced changes have been implemented. The LACP configuration now seems to work persistently. Thank you for your understanding..</p> <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - Due to ongoing stability issues with our current environment, the IP router will be completely restructured. With this we want to solve the problems in the long term and revive our old usual quality in terms of uptime. Important changes will therefore be made during the specified period to counteract the downtimes. Changes: \- Reinstallation of the router on Bare Metal Debian without Proxmox (virtual environment) to avoid overhead \- Setup of redundant NIC to minimize the risk of failure We hope for your understanding and would like to improve the uptime for you in the long term massive..</p> <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>19:28:00</var> GMT+0</small><br><strong>Identified</strong> - We are starting..</p> <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>20:54:37</var> GMT+0</small><br><strong>Identified</strong> - Due to turbulences with the PXE in LACP mode, there will be a delay in completion. we are actively working on this and will inform you as soon as the maintenance has been successfully completed..</p> ]]> Wed, 28 Aug 2024 19:00:00 +0000 https://vapp.instatus.com/maintenance/cm0bhumuf005i7x0t0gnax65y https://vapp.instatus.com/maintenance/cm0bhumuf005i7x0t0gnax65y IPv6 Connections not Working Type: Incident Duration: 5 hours and 42 minutes Aug 26, 16:12:25 GMT+0 - Resolved - Cause bypassed. Customers will be informed for further steps if necessary. Aug 26, 15:28:00 GMT+0 - Identified - The IPv6 block does not appear to be usable from the OVH side and therefore cannot be used. Type: Incident

Duration: 5 hours and 42 minutes

<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>16:12:25</var> GMT+0</small><br><strong>Resolved</strong> - Cause bypassed. Customers will be informed for further steps if necessary..</p> <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>15:28:00</var> GMT+0</small><br><strong>Identified</strong> - The IPv6 block does not appear to be usable from the OVH side and therefore cannot be used..</p> ]]> Mon, 26 Aug 2024 15:28:00 +0000 https://vapp.instatus.com/incident/cm0b5l17o0002og766d5n9xoy https://vapp.instatus.com/incident/cm0b5l17o0002og766d5n9xoy [S2] PVE2, [S2] IP Router 1 & servers.plotnic.de Outage Type: Incident Duration: 3 days, 21 hours and 55 minutes Aug 25, 14:33:08 GMT+0 - Investigating - \[S2\] PVE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Aug 25, 14:47:46 GMT+0 - Investigating - Kernel Panic happened. Reason unknown. We are continuing to work on a fix for this incident. The services are back Operational at first. Aug 29, 12:28:15 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 days, 21 hours and 55 minutes

<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>14:33:08</var> GMT+0</small><br><strong>Investigating</strong> - \[S2\] PVE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>14:47:46</var> GMT+0</small><br><strong>Investigating</strong> - Kernel Panic happened. Reason unknown. We are continuing to work on a fix for this incident. The services are back Operational at first..</p> <p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>12:28:15</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 25 Aug 2024 14:33:08 +0000 https://vapp.instatus.com/incident/cm09o5ts800drjha7vimxmor1 https://vapp.instatus.com/incident/cm09o5ts800drjha7vimxmor1