VoxiHost Status - Incident history https://voxihost.instatus.com VoxiHost Mon, 17 Aug 2026 23:30:00 +0000 Scheduled Maintenance - Node Reboot Type: Maintenance Duration: 9 minutes Affected Components: Node #1 (Germany/FRA) Aug 17, 11:28:48 GMT+0 - Identified - We will be performing scheduled maintenance on **August 18, 2026**, starting at **01:30** (**Warsaw/CEST time**) to apply routine system updates and infrastructure improvements. All VPS instances hosted on this node will be offline during this window. **Expected downtime: approximately 5-10 minutes.** No action is required on customers end. **We apologize for any inconvenience and appreciate your patience.** Aug 17, 23:30:01 GMT+0 - Identified - Maintenance is now in progress Aug 17, 23:38:57 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 9 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>11:28:48</var> GMT+0</small><br><strong>Identified</strong> - We will be performing scheduled maintenance on **August 18, 2026**, starting at **01:30** (**Warsaw/CEST time**) to apply routine system updates and infrastructure improvements. All VPS instances hosted on this node will be offline during this window. **Expected downtime: approximately 5-10 minutes.** No action is required on customers end. **We apologize for any inconvenience and appreciate your patience.**.</p> <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>23:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>23:38:57</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Mon, 17 Aug 2026 23:30:00 +0000 https://voxihost.instatus.com/maintenance/cmsx5hsxi008n0zpweyy6tmgx https://voxihost.instatus.com/maintenance/cmsx5hsxi008n0zpweyy6tmgx Scheduled Maintenance - Node Reboot Type: Maintenance Duration: 25 minutes Affected Components: Node #1 (Germany/FRA) Jul 20, 22:54:20 GMT+0 - Identified - We will be performing scheduled maintenance on **July 22, 2026**, starting at **01:00** (**Warsaw/CEST time**) to apply routine system updates and infrastructure improvements. All VPS instances hosted on this node will be offline during this window. **Expected downtime: approximately 5-10 minutes.** No action is required on customers end. **We apologize for any inconvenience and appreciate your patience.** Jul 21, 23:01:46 GMT+0 - Identified - Maintenance is now in progress. Jul 21, 23:06:54 GMT+0 - Identified - We are in the process of safely shutting down all customer VMs before rebooting the node. Jul 21, 23:14:04 GMT+0 - Identified - The host reboot is complete. We are now powering on all customer VMs. Jul 21, 23:26:50 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 25 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 20</var>, <var data-var='time'>22:54:20</var> GMT+0</small><br><strong>Identified</strong> - We will be performing scheduled maintenance on **July 22, 2026**, starting at **01:00** (**Warsaw/CEST time**) to apply routine system updates and infrastructure improvements. All VPS instances hosted on this node will be offline during this window. **Expected downtime: approximately 5-10 minutes.** No action is required on customers end. **We apologize for any inconvenience and appreciate your patience.**.</p> <p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>23:01:46</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>23:06:54</var> GMT+0</small><br><strong>Identified</strong> - We are in the process of safely shutting down all customer VMs before rebooting the node..</p> <p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>23:14:04</var> GMT+0</small><br><strong>Identified</strong> - The host reboot is complete. We are now powering on all customer VMs..</p> <p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>23:26:50</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Tue, 21 Jul 2026 23:00:00 +0000 https://voxihost.instatus.com/maintenance/cmrttnkcw02kd0ypcmcxmu2y6 https://voxihost.instatus.com/maintenance/cmrttnkcw02kd0ypcmcxmu2y6 Network stability fixes Type: Maintenance Duration: 23 minutes Affected Components: Node #1 (Germany/FRA) May 30, 23:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. May 29, 22:29:34 GMT+0 - Identified - We are moving maintenance to next day 31.05.2026 01:00 CET. May 30, 23:00:01 GMT+0 - Identified - Maintenance is now in progress May 30, 23:22:33 GMT+0 - Completed - **Maintenance completed successfully!** We are not forcing any reboots to protect your current uptime. However, for the optimizations to take full effect, we highly recommend that you manually shut down your VPS via the dashboard and start it again. Look out for an email from us with more details shortly. Type: Maintenance

Duration: 23 minutes

Affected Components:

<p><small>May <var data-var='date'> 30</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>22:29:34</var> GMT+0</small><br><strong>Identified</strong> - We are moving maintenance to next day 31.05.2026 01:00 CET..</p> <p><small>May <var data-var='date'> 30</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 30</var>, <var data-var='time'>23:22:33</var> GMT+0</small><br><strong>Completed</strong> - **Maintenance completed successfully!** We are not forcing any reboots to protect your current uptime. However, for the optimizations to take full effect, we highly recommend that you manually shut down your VPS via the dashboard and start it again. Look out for an email from us with more details shortly..</p> ]]> Sat, 30 May 2026 23:00:00 +0000 https://voxihost.instatus.com/maintenance/cmprgak1701k1qxjs851o848p https://voxihost.instatus.com/maintenance/cmprgak1701k1qxjs851o848p Dashboard update (Tickets/Affiliate Program/Design improvements) Type: Maintenance Duration: 1 hour and 18 minutes Affected Components: VPS Panel May 26, 18:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. May 26, 18:00:01 GMT+0 - Identified - Maintenance is now in progress May 26, 19:17:36 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 1 hour and 18 minutes

Affected Components:

<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>19:17:36</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Tue, 26 May 2026 18:00:00 +0000 https://voxihost.instatus.com/maintenance/cmpmrlj6c0euinrlti9hszy2a https://voxihost.instatus.com/maintenance/cmpmrlj6c0euinrlti9hszy2a Investigating this incident Type: Incident Duration: 13 minutes Affected Components: Node #1 (Germany/FRA) May 2, 22:34:04 GMT+0 - Investigating - We are currently investigating this incident. May 2, 22:37:22 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 2, 22:39:41 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 2, 22:47:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 13 minutes

Affected Components:

<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>22:34:04</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>22:37:22</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>22:39:41</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>22:47:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 2 May 2026 22:34:04 +0000 https://voxihost.instatus.com/incident/cmoox57gp03r5ue1eg60cmm3a https://voxihost.instatus.com/incident/cmoox57gp03r5ue1eg60cmm3a Maintenance (Security Patch) Type: Maintenance Duration: 38 minutes Affected Components: VPS Panel Apr 12, 23:41:00 GMT+0 - Identified - In progress Apr 12, 23:41:01 GMT+0 - Identified - Maintenance is now in progress Apr 13, 00:19:00 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 38 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>23:41:00</var> GMT+0</small><br><strong>Identified</strong> - In progress.</p> <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>23:41:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>00:19:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Sun, 12 Apr 2026 23:41:00 +0000 https://voxihost.instatus.com/maintenance/cmnwfii0h02x3hrz5zzvlrstw https://voxihost.instatus.com/maintenance/cmnwfii0h02x3hrz5zzvlrstw Hourly Deployment & UI Changes Type: Maintenance Duration: 25 minutes Affected Components: VPS Panel Apr 9, 19:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Apr 9, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 9, 19:25:23 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 25 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>19:25:23</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 9 Apr 2026 19:00:00 +0000 https://voxihost.instatus.com/maintenance/cmnrskhtx01vrzia826xrnyyd https://voxihost.instatus.com/maintenance/cmnrskhtx01vrzia826xrnyyd VNC Support Type: Maintenance Duration: 15 minutes Affected Components: VPS Panel Mar 18, 14:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time to add VNC Support. Mar 18, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 18, 14:15:28 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 15 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time to add VNC Support..</p> <p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>14:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>14:15:28</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Wed, 18 Mar 2026 14:00:00 +0000 https://voxihost.instatus.com/maintenance/cmmw3groo09r2w3c7mpbruncp https://voxihost.instatus.com/maintenance/cmmw3groo09r2w3c7mpbruncp DDoS Attack Type: Incident Duration: 45 minutes Affected Components: Node #1 (Germany/FRA), Anti-DDoS Protection Mar 11, 20:39:17 GMT+0 - Investigating - We are currently investigating this incident. Mar 11, 20:40:13 GMT+0 - Identified - We are continuing to work on a fix for this incident. **Connection is back.** Mar 11, 20:45:42 GMT+0 - Monitoring - We are currently monitoring the situation, from what we currently know there was an DDoS attack with bypassed [PletX.net](http://PletX.net) protection. Mar 11, 21:24:09 GMT+0 - Resolved - This incident has been resolved. We have provided everything needed to resolve the **DDoS Bypass** used to [PletX.net](http://PletX.net), on our end everything is back & working stable. Type: Incident

Duration: 45 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>20:39:17</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>20:40:13</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. **Connection is back.**.</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>20:45:42</var> GMT+0</small><br><strong>Monitoring</strong> - We are currently monitoring the situation, from what we currently know there was an DDoS attack with bypassed [PletX.net](http://PletX.net) protection..</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>21:24:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. We have provided everything needed to resolve the **DDoS Bypass** used to [PletX.net](http://PletX.net), on our end everything is back & working stable..</p> ]]> Wed, 11 Mar 2026 20:39:17 +0000 https://voxihost.instatus.com/incident/cmmmi5b3e0044ghn1wclh3unm https://voxihost.instatus.com/incident/cmmmi5b3e0044ghn1wclh3unm Unknown instability Type: Incident Duration: 31 minutes Affected Components: VPS Panel Mar 5, 22:08:43 GMT+0 - Investigating - We are currently investigating this incident. Mar 5, 22:11:20 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 5, 22:39:30 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 31 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>22:08:43</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>22:11:20</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>22:39:30</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. .</p> ]]> Thu, 5 Mar 2026 22:08:43 +0000 https://voxihost.instatus.com/incident/cmme0p7cp16xn50p1rqjy8b9w https://voxihost.instatus.com/incident/cmme0p7cp16xn50p1rqjy8b9w PletX Network Issues Type: Incident Duration: 1 hour and 4 minutes Affected Components: Anti-DDoS Protection Feb 16, 21:29:28 GMT+0 - Resolved - This incident has been resolved. We don't see any more packet loss/drops. Feb 16, 20:25:23 GMT+0 - Monitoring - We are monitoring current PletX disconnects caused by larger DDoS Attacks on their network and specific ingress paths not being able to handle it correctly. It seems like disconnects are very random and take 1/2s to recover. Type: Incident

Duration: 1 hour and 4 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>21:29:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. We don't see any more packet loss/drops..</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>20:25:23</var> GMT+0</small><br><strong>Monitoring</strong> - We are monitoring current PletX disconnects caused by larger DDoS Attacks on their network and specific ingress paths not being able to handle it correctly. It seems like disconnects are very random and take 1/2s to recover..</p> ]]> Mon, 16 Feb 2026 20:25:23 +0000 https://voxihost.instatus.com/incident/cmlpmitza03p014oy3jljo9pz https://voxihost.instatus.com/incident/cmlpmitza03p014oy3jljo9pz Infrastructure failure Type: Incident Duration: 5 days, 3 hours and 42 minutes Affected Components: VPS Panel, Node #1 (Germany/FRA), , Strona Główna, Inne → Dec 30, 22:55:49 GMT+0 - Investigating - We are currently running disk check, to verify the issue. Dec 31, 00:29:20 GMT+0 - Investigating - We are currently recovering customer files, all data is being transferred to safe-drive. After that we will continue investigating. Dec 31, 01:11:38 GMT+0 - Investigating - We can confirm that all customers data was safely extracted. This is yet to be confirmed later... no data on customers servers should have been affected as our alert system indicates that most VPS servers weren't touched by any error in terms of drive, and those that were went into read-only lockdown! I'm still looking into fixing this as fast possible. **Daniel M.** **CEO VoxiHost** Dec 31, 07:36:54 GMT+0 - Identified - Dear Customers, I am writing this with a heavy heart and complete honesty. I have been fighting this critical failure for the past 10 hours, but I have actually been on my feet for over 24 hours now. What started as a simple disk alert has ended in a broken Proxmox backend, affecting every single VPS and our own internal systems. I was deeply optimistic at first because the file sizes looked correct, but I have now discovered that many of them are severely corrupted. Our internal systems, including the billing panel and database, have also been hit. Since our internal backups run on a 7-day cycle and the next one was due exactly at the end of today, some recent account changes or new registrations from the last few days are currently missing. However, I want to reassure you that your funds are safe. Once everything is stable, I will manually verify all transactions through our payment providers to ensure every credit and service is correctly restored. Regarding your data, I am doing everything possible to recover what can be saved. For those whose data is unfortunately unrecoverable on our end, I will be sending an email shortly with a download link to your raw VPS disk image so you can perform your own analysis and potential recovery. For those whose servers were partially saved, I will provide a fresh, functional disk along with a compressed archive of your salvaged files. **As a one-man army building this hosting dream, this situation is devastating to me. I have reached a point of total exhaustion and I need to take a short break to sleep at least 2 hours and spend some time with my family for New Year’s Day. I need to recharge my mind to avoid making any critical mistakes during the rest of this recovery process. I will be back at work in full force very soon. I cannot express how sorry I am for this catastrophe and I thank you for your patience and for staying with me during this dark hour.** Best regards, Daniel M. VoxiHost **I'm sorry... i will try my best to find a way for compensation once this is all done.** Dec 31, 02:36:29 GMT+0 - Identified - After comprehensive diagnostics and data recovery operations, we have determined that the host system corruption is unrecoverable through repair. We are proceeding with a clean Proxmox reinstallation. * **All customer data has been successfully backed up to secure offsite storage** * **Preliminary analysis indicates no customer VM data corruption** * **RAID arrays verified healthy - no hardware failures detected** **Root Cause:** The cause of the corruption is still under investigation. Logs and diagnostics have been preserved for detailed analysis after service restoration. **Our Priority:** Restoring all customer services as quickly as possible. Full post-mortem analysis will follow once services are back online. **ETA:** Services resuming within 2-3 hours. Dec 30, 21:53:09 GMT+0 - Investigating - We are currently investigating this incident. Dec 31, 14:38:54 GMT+0 - Identified - **Update on the current situation** I have analyzed all VM disk dumps and, as mentioned before, I was only partially able to recover data from them. I am currently on a train to spend New Year's Eve with someone close to recharge. Before leaving, I managed to restore our mailing system, which means you can now contact us again at **support@voxihost.pl**. I have also created a dedicated email for recovery and compensation: **recovery@voxihost.pl**. From this address, users will receive more information regarding the next steps and their data. If I find the time, I will start sending informational emails within the next 2-3 hours, but I cannot promise that yet. I will do my best to be back at work as soon as possible, likely late on January 1st or on January 2nd. I sincerely apologize again for this entire situation. I will do everything in my power to bring everything back to life and compensate everyone affected. Best regards, Daniel M. VoxiHost Jan 2, 16:43:20 GMT+0 - Identified - Update! Working on sending emails to all customers. Please check your inboxes within 2-5h. Jan 4, 14:36:42 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jan 2, 20:55:08 GMT+0 - Identified - Emails were delivered from **recovery@voxihost.pl,** if you don't see one check your **SPAM**! Jan 9, 19:48:04 GMT+0 - Identified - Hey, just wanted to drop quick update on the situation! I'm almost done with implementing new front-page, on the backend stuff i already setuped multiple backup solutions that preform global node backup every 1 day to prevent such situations... **Best regards, Daniel Marszałkowski** **CEO VoxiHost** Jan 15, 14:36:57 GMT+0 - Identified - I have deployed our front-page back and working! **(New Design)** **I'm still working on bringing back the customer panel!** **Best regards, Daniel Marszałkowski** **CEO VoxiHost** Feb 8, 15:28:00 GMT+0 - Identified - We are currently finalizing our new Customer Panel. While the setup is taking a bit longer than expected, we remain partly operational accepting orders and delivering VPS services. _I expect to launch the new panel by the end of this week!_ **Best regards, Daniel Marszałkowski** **CEO VoxiHost** Mar 5, 01:35:27 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 days, 3 hours and 42 minutes

Affected Components: , , ,

<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>22:55:49</var> GMT+0</small><br><strong>Investigating</strong> - We are currently running disk check, to verify the issue..</p> <p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>00:29:20</var> GMT+0</small><br><strong>Investigating</strong> - We are currently recovering customer files, all data is being transferred to safe-drive. After that we will continue investigating..</p> <p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>01:11:38</var> GMT+0</small><br><strong>Investigating</strong> - We can confirm that all customers data was safely extracted. This is yet to be confirmed later... no data on customers servers should have been affected as our alert system indicates that most VPS servers weren't touched by any error in terms of drive, and those that were went into read-only lockdown! I'm still looking into fixing this as fast possible. **Daniel M.** **CEO VoxiHost**.</p> <p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>07:36:54</var> GMT+0</small><br><strong>Identified</strong> - Dear Customers, I am writing this with a heavy heart and complete honesty. I have been fighting this critical failure for the past 10 hours, but I have actually been on my feet for over 24 hours now. What started as a simple disk alert has ended in a broken Proxmox backend, affecting every single VPS and our own internal systems. I was deeply optimistic at first because the file sizes looked correct, but I have now discovered that many of them are severely corrupted. Our internal systems, including the billing panel and database, have also been hit. Since our internal backups run on a 7-day cycle and the next one was due exactly at the end of today, some recent account changes or new registrations from the last few days are currently missing. However, I want to reassure you that your funds are safe. Once everything is stable, I will manually verify all transactions through our payment providers to ensure every credit and service is correctly restored. Regarding your data, I am doing everything possible to recover what can be saved. For those whose data is unfortunately unrecoverable on our end, I will be sending an email shortly with a download link to your raw VPS disk image so you can perform your own analysis and potential recovery. For those whose servers were partially saved, I will provide a fresh, functional disk along with a compressed archive of your salvaged files. **As a one-man army building this hosting dream, this situation is devastating to me. I have reached a point of total exhaustion and I need to take a short break to sleep at least 2 hours and spend some time with my family for New Year’s Day. I need to recharge my mind to avoid making any critical mistakes during the rest of this recovery process. I will be back at work in full force very soon. I cannot express how sorry I am for this catastrophe and I thank you for your patience and for staying with me during this dark hour.** Best regards, Daniel M. VoxiHost **I'm sorry... i will try my best to find a way for compensation once this is all done.**.</p> <p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>02:36:29</var> GMT+0</small><br><strong>Identified</strong> - After comprehensive diagnostics and data recovery operations, we have determined that the host system corruption is unrecoverable through repair. We are proceeding with a clean Proxmox reinstallation. * **All customer data has been successfully backed up to secure offsite storage** * **Preliminary analysis indicates no customer VM data corruption** * **RAID arrays verified healthy - no hardware failures detected** **Root Cause:** The cause of the corruption is still under investigation. Logs and diagnostics have been preserved for detailed analysis after service restoration. **Our Priority:** Restoring all customer services as quickly as possible. Full post-mortem analysis will follow once services are back online. **ETA:** Services resuming within 2-3 hours..</p> <p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>21:53:09</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 31</var>, <var data-var='time'>14:38:54</var> GMT+0</small><br><strong>Identified</strong> - **Update on the current situation** I have analyzed all VM disk dumps and, as mentioned before, I was only partially able to recover data from them. I am currently on a train to spend New Year's Eve with someone close to recharge. Before leaving, I managed to restore our mailing system, which means you can now contact us again at **support@voxihost.pl**. I have also created a dedicated email for recovery and compensation: **recovery@voxihost.pl**. From this address, users will receive more information regarding the next steps and their data. If I find the time, I will start sending informational emails within the next 2-3 hours, but I cannot promise that yet. I will do my best to be back at work as soon as possible, likely late on January 1st or on January 2nd. I sincerely apologize again for this entire situation. I will do everything in my power to bring everything back to life and compensate everyone affected. Best regards, Daniel M. VoxiHost.</p> <p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>16:43:20</var> GMT+0</small><br><strong>Identified</strong> - Update! Working on sending emails to all customers. Please check your inboxes within 2-5h..</p> <p><small>Jan <var data-var='date'> 4</var>, <var data-var='time'>14:36:42</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>20:55:08</var> GMT+0</small><br><strong>Identified</strong> - Emails were delivered from **recovery@voxihost.pl,** if you don't see one check your **SPAM**!.</p> <p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>19:48:04</var> GMT+0</small><br><strong>Identified</strong> - Hey, just wanted to drop quick update on the situation! I'm almost done with implementing new front-page, on the backend stuff i already setuped multiple backup solutions that preform global node backup every 1 day to prevent such situations... **Best regards, Daniel Marszałkowski** **CEO VoxiHost**.</p> <p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>14:36:57</var> GMT+0</small><br><strong>Identified</strong> - I have deployed our front-page back and working! **(New Design)** **I'm still working on bringing back the customer panel!** **Best regards, Daniel Marszałkowski** **CEO VoxiHost**.</p> <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>15:28:00</var> GMT+0</small><br><strong>Identified</strong> - We are currently finalizing our new Customer Panel. While the setup is taking a bit longer than expected, we remain partly operational accepting orders and delivering VPS services. _I expect to launch the new panel by the end of this week!_ **Best regards, Daniel Marszałkowski** **CEO VoxiHost**.</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>01:35:27</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 30 Dec 2025 21:53:09 +0000 https://voxihost.instatus.com/incident/cmjt4it0k01uuhe9e2o5680zr https://voxihost.instatus.com/incident/cmjt4it0k01uuhe9e2o5680zr KVM Configuration Change: Enabling Host-Passthrough Type: Maintenance Duration: 5 minutes Affected Components: Node #1 (Germany/FRA) Dec 21, 19:00:00 GMT+0 - Identified - **Summary:** We are upgrading the virtualization architecture across our **entire fleet** to standardise high-performance settings for all clients. **Details:** In 5 hours, we will begin rolling out a configuration update to switch the CPU models from ``` kvm64 ``` to ``` Host-Passthrough ``` on **all nodes**. This change eliminates emulation overhead and exposes advanced instruction sets (AVX2, AVX-512, AES-NI) directly to your VPS, unlocking maximum hardware performance for everyone. **Impact:** * **Scope:** **All VPS instances** (Budget & Premium) running on legacy configuration. * **Action:** A quick system reboot is required to apply the new CPU flags. * **Downtime:** Expected unavailability is **less than 1 minute** per instance. We are committed to providing the best possible performance for every service hosted with **VoxiHost**. Dec 21, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 21, 19:05:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 5 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - **Summary:** We are upgrading the virtualization architecture across our **entire fleet** to standardise high-performance settings for all clients. **Details:** In 5 hours, we will begin rolling out a configuration update to switch the CPU models from ``` kvm64 ``` to ``` Host-Passthrough ``` on **all nodes**. This change eliminates emulation overhead and exposes advanced instruction sets (AVX2, AVX-512, AES-NI) directly to your VPS, unlocking maximum hardware performance for everyone. **Impact:** * **Scope:** **All VPS instances** (Budget & Premium) running on legacy configuration. * **Action:** A quick system reboot is required to apply the new CPU flags. * **Downtime:** Expected unavailability is **less than 1 minute** per instance. We are committed to providing the best possible performance for every service hosted with **VoxiHost**..</p> <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>19:05:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sun, 21 Dec 2025 19:00:00 +0000 https://voxihost.instatus.com/maintenance/cmjftrmum03sbnccjjjqjlrp6 https://voxihost.instatus.com/maintenance/cmjftrmum03sbnccjjjqjlrp6 Node Reboot for Guaranteed CPU Performance Baseline Type: Maintenance Duration: 10 minutes Affected Components: VPS Panel, Node #1 (Germany/FRA), Strona Główna Nov 4, 23:00:00 GMT+0 - Identified - **Impact:** Users will experience **a brief, single service interruption** as the server node performs a necessary reboot. **Reason for Reboot:** We are updating the server's kernel configuration to switch the CPU from an **energy-saving profile** to a **performance-guaranteed profile**. This crucial change ensures the system strictly maintains a **4.2 GHz minimum clock speed** for predictable, low-latency VM performance. Crucially, the system **retains the ability to dynamically boost up to 5.7 GHz** when needed for demanding tasks. We apologize for the brief downtime and are committed to maximizing the reliability of your services. Nov 4, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 4, 23:11:00 GMT+0 - Completed - The scheduled infrastructure maintenance is now **complete**. The Node's CPU control settings were updated successfully. ### Maintenance Summary The system's power-saving profile was switched to a guaranteed high-performance profile. * **Minimum Frequency (Baseline):** **4.2 GHz** * **Maximum Frequency (Turbo):** **5.759 GHz** ### Benefit Summary * **Zero Latency Jitter:** The deep idle state was eliminated, ensuring services receive **instantaneous power** when requested. * **Predictable Consistency:** The Node now maintains a **4.2 GHz baseline**, minimizing performance variance across all virtual machines. Nov 4, 23:10:00 GMT+0 - Identified - We are making sure that configuration was applied correctly, all VPS servers are back working. Nov 4, 23:12:00 GMT+0 - Completed - **Hey, Daniel here!** I wanted to add a small additional note regarding the maintenance i performed. Today, I observed some weird behavior with the CPU frequency on the server node specifically, the clock speed was dropping dramatically, sometimes as low as 400 MHz, before instantly jumping back up to 4 GHz+. I traced this issue to the default Energy Performance Preference (EPP) settings, which were aggressively trying to save power during minimal idle times. While good for laptops, on a server with many running VPS instances, this rapid frequency oscillation was causing a noticeable increase in latency and unpredictable performance. I decided to fix this immediately, performing the necessary kernel changes overnight to only affect a small customer base during EU hours. As my goal is to guarantee the best, most consistent performance possible for all our VPS customers, I have overridden the default power profile. The server is now locked to a high-performance profile with a guaranteed minimum baseline of 4.2 GHz, ensuring zero lag and maximum stability for your services. Type: Maintenance

Duration: 10 minutes

Affected Components: , ,

<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Identified</strong> - **Impact:** Users will experience **a brief, single service interruption** as the server node performs a necessary reboot. **Reason for Reboot:** We are updating the server's kernel configuration to switch the CPU from an **energy-saving profile** to a **performance-guaranteed profile**. This crucial change ensures the system strictly maintains a **4.2 GHz minimum clock speed** for predictable, low-latency VM performance. Crucially, the system **retains the ability to dynamically boost up to 5.7 GHz** when needed for demanding tasks. We apologize for the brief downtime and are committed to maximizing the reliability of your services..</p> <p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>23:11:00</var> GMT+0</small><br><strong>Completed</strong> - The scheduled infrastructure maintenance is now **complete**. The Node's CPU control settings were updated successfully. ### Maintenance Summary The system's power-saving profile was switched to a guaranteed high-performance profile. * **Minimum Frequency (Baseline):** **4.2 GHz** * **Maximum Frequency (Turbo):** **5.759 GHz** ### Benefit Summary * **Zero Latency Jitter:** The deep idle state was eliminated, ensuring services receive **instantaneous power** when requested. * **Predictable Consistency:** The Node now maintains a **4.2 GHz baseline**, minimizing performance variance across all virtual machines..</p> <p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>23:10:00</var> GMT+0</small><br><strong>Identified</strong> - We are making sure that configuration was applied correctly, all VPS servers are back working..</p> <p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>23:12:00</var> GMT+0</small><br><strong>Completed</strong> - **Hey, Daniel here!** I wanted to add a small additional note regarding the maintenance i performed. Today, I observed some weird behavior with the CPU frequency on the server node specifically, the clock speed was dropping dramatically, sometimes as low as 400 MHz, before instantly jumping back up to 4 GHz+. I traced this issue to the default Energy Performance Preference (EPP) settings, which were aggressively trying to save power during minimal idle times. While good for laptops, on a server with many running VPS instances, this rapid frequency oscillation was causing a noticeable increase in latency and unpredictable performance. I decided to fix this immediately, performing the necessary kernel changes overnight to only affect a small customer base during EU hours. As my goal is to guarantee the best, most consistent performance possible for all our VPS customers, I have overridden the default power profile. The server is now locked to a high-performance profile with a guaranteed minimum baseline of 4.2 GHz, ensuring zero lag and maximum stability for your services..</p> ]]> Tue, 4 Nov 2025 23:00:00 +0000 https://voxihost.instatus.com/maintenance/cmhl488ec01j511qp2fp782rv https://voxihost.instatus.com/maintenance/cmhl488ec01j511qp2fp782rv NeoProtect, outage Type: Incident Duration: 17 hours and 3 minutes Affected Components: , Anti-DDoS Protection, Datacenter → Oct 31, 17:55:41 GMT+0 - Postmortem - A major service interruption occurred starting at 21:45:00 on October 30th. The root cause was an external, critical failure at our former DDoS Protection vendor, NeoProtect Remote Shield. NeoProtect's upstream provider, CDN77 / Datapacket, disabled all active BGP sessions towards the NeoProtect network, instantly causing all services protected by their Remote Shield to become unrouteable and unavailable. Our resolution involved an emergency network migration: 1. We attempted to route raw network traffic via Amsterdam as a temporary fix, but complex routing issues prevented immediate deployment overnight. 2. We successfully established contact with a new DDoS Protection partner, PletX.net, and performed a full, critical network swap. 3. Service was fully restored at 13:53:24 on October 31st. Outcome: VoxiHost has permanently migrated to PletX.net for DDoS protection as NeoProtect has since discontinued its Remote Shield service. We are implementing a raw-network standby failover with our DC provider to prevent future external vendor failures from causing extended downtime. Oct 30, 20:45:00 GMT+0 - Investigating - We are currently investigating this incident. Oct 30, 20:47:00 GMT+0 - Identified - We have identified to be a global outage from NeoProtect <https://status.neoprotect.net/incidents/kdmtx0wk3h1l> Oct 30, 21:34:00 GMT+0 - Identified - Provided information by NeoProtect: "Our Upstream CDN77 / Datapacket has deactivated all BGP sessions towards our network. This results in full downtime of all associated services such as all Remote Shield customers (aside from XC customers in AMS). The ETR given by them at this time is "tomorrow", we are trying to get this reconsidered but we do not estimate for reconsideration to happen in our favor." We are trying our best to get around this and deploy PletX DDoS Protection with will replace NeoProtect Oct 31, 00:21:18 GMT+0 - Identified - We are awaiting for [PletX.net](http://PletX.net) routing & whitelist to be configured, to replace NeoProtect. Oct 31, 12:53:24 GMT+0 - Monitoring - We are currently, on PletX protection & networking. Everything should be back to normal! Oct 31, 01:12:20 GMT+0 - Identified - We are looking forward into having this issue solved in the morning EU time, we will be trying to get it replaced as soon as possible once PletX team wakes up and can preform the setup. This issue with NeoProtect wasn't expected at all, since their provider pulled a 'plug' on them and disconnected BGP sessions leaving us completely stranded and many other companies. We hope for full understanding from our customers, and we will take all important steps to provide compensation & make stuff right after this hard time... Oct 31, 13:48:09 GMT+0 - Resolved - This incident has been resolved. As from now on we will be using [PletX.net](http://PletX.net) DDoS Protection. Soon there will be postmortem about this incident and more information for the summary. Type: Incident

Duration: 17 hours and 3 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>17:55:41</var> GMT+0</small><br><strong>Postmortem</strong> - A major service interruption occurred starting at 21:45:00 on October 30th. The root cause was an external, critical failure at our former DDoS Protection vendor, NeoProtect Remote Shield. NeoProtect's upstream provider, CDN77 / Datapacket, disabled all active BGP sessions towards the NeoProtect network, instantly causing all services protected by their Remote Shield to become unrouteable and unavailable. Our resolution involved an emergency network migration: 1. We attempted to route raw network traffic via Amsterdam as a temporary fix, but complex routing issues prevented immediate deployment overnight. 2. We successfully established contact with a new DDoS Protection partner, PletX.net, and performed a full, critical network swap. 3. Service was fully restored at 13:53:24 on October 31st. Outcome: VoxiHost has permanently migrated to PletX.net for DDoS protection as NeoProtect has since discontinued its Remote Shield service. We are implementing a raw-network standby failover with our DC provider to prevent future external vendor failures from causing extended downtime..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:45:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:47:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified to be a global outage from NeoProtect <https://status.neoprotect.net/incidents/kdmtx0wk3h1l>.</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>21:34:00</var> GMT+0</small><br><strong>Identified</strong> - Provided information by NeoProtect: "Our Upstream CDN77 / Datapacket has deactivated all BGP sessions towards our network. This results in full downtime of all associated services such as all Remote Shield customers (aside from XC customers in AMS). The ETR given by them at this time is "tomorrow", we are trying to get this reconsidered but we do not estimate for reconsideration to happen in our favor." We are trying our best to get around this and deploy PletX DDoS Protection with will replace NeoProtect.</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>00:21:18</var> GMT+0</small><br><strong>Identified</strong> - We are awaiting for [PletX.net](http://PletX.net) routing & whitelist to be configured, to replace NeoProtect..</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>12:53:24</var> GMT+0</small><br><strong>Monitoring</strong> - We are currently, on PletX protection & networking. Everything should be back to normal!.</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>01:12:20</var> GMT+0</small><br><strong>Identified</strong> - We are looking forward into having this issue solved in the morning EU time, we will be trying to get it replaced as soon as possible once PletX team wakes up and can preform the setup. This issue with NeoProtect wasn't expected at all, since their provider pulled a 'plug' on them and disconnected BGP sessions leaving us completely stranded and many other companies. We hope for full understanding from our customers, and we will take all important steps to provide compensation & make stuff right after this hard time....</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>13:48:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. As from now on we will be using [PletX.net](http://PletX.net) DDoS Protection. Soon there will be postmortem about this incident and more information for the summary..</p> ]]> Thu, 30 Oct 2025 20:45:00 +0000 https://voxihost.instatus.com/incident/cmhe3u8xx00ni41ulfqm06e1c https://voxihost.instatus.com/incident/cmhe3u8xx00ni41ulfqm06e1c Correction/Changes in BIOS configuration Type: Maintenance Duration: 14 minutes Affected Components: VPS Panel, Node #1 (Germany/FRA), Strona Główna Oct 30, 00:00:00 GMT+0 - Identified - We will be working on changing DDR5 RAM clock speed from 3600 & 4800MT/s to 5200 MT/s. This will bring better performance for RAM using applications etc. We will be also looking into some additional configurations in the BIOS. This should take up to 30min, we will try to be as fast as possible :) Oct 30, 00:00:01 GMT+0 - Identified - Konserwacja jest teraz w toku Oct 30, 00:13:39 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 14 minutes

Affected Components: , ,

<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> - We will be working on changing DDR5 RAM clock speed from 3600 & 4800MT/s to 5200 MT/s. This will bring better performance for RAM using applications etc. We will be also looking into some additional configurations in the BIOS. This should take up to 30min, we will try to be as fast as possible :).</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> - Konserwacja jest teraz w toku.</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>00:13:39</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 30 Oct 2025 00:00:00 +0000 https://voxihost.instatus.com/maintenance/cmhc773sa003tbh4awxb2ivll https://voxihost.instatus.com/maintenance/cmhc773sa003tbh4awxb2ivll Router Reboot Type: Maintenance Duration: 10 minutes Affected Components: Node #1 (Germany/FRA), VPS Panel, Strona Główna Oct 20, 17:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Oct 20, 17:00:01 GMT+0 - Identified - Konserwacja jest teraz w toku Oct 20, 17:10:00 GMT+0 - Completed - Konserwacja zakończyła się pomyślnie Type: Maintenance

Duration: 10 minutes

Affected Components: , ,

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> - Konserwacja jest teraz w toku.</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>17:10:00</var> GMT+0</small><br><strong>Completed</strong> - Konserwacja zakończyła się pomyślnie.</p> ]]> Mon, 20 Oct 2025 17:00:00 +0000 https://voxihost.instatus.com/maintenance/cmgz551j5028qmx24aoj2jt97 https://voxihost.instatus.com/maintenance/cmgz551j5028qmx24aoj2jt97 #1 Update 'New Feature & Upgrades (01.09.2025-08.10.2025)' Type: Maintenance Duration: 1 hour and 11 minutes Affected Components: VPS Panel Oct 8, 12:00:01 GMT+0 - Identified - Konserwacja jest teraz w toku Oct 8, 08:47:11 GMT+0 - Identified - We have to delay this by 1h to make sure we are fully ready for changes to be made. Oct 8, 09:55:49 GMT+0 - Identified - Again we had to delay this update, we were affected by some very important issues. Working on fix and will try to push this out as fast as we can :) Oct 8, 13:10:39 GMT+0 - Completed - Maintenance has completed successfully. Oct 8, 12:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time, to preform panel update with new features! More information can be found on our https://discord.gg/U5VuePpsEF Type: Maintenance

Duration: 1 hour and 11 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br><strong>Identified</strong> - Konserwacja jest teraz w toku.</p> <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>08:47:11</var> GMT+0</small><br><strong>Identified</strong> - We have to delay this by 1h to make sure we are fully ready for changes to be made..</p> <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>09:55:49</var> GMT+0</small><br><strong>Identified</strong> - Again we had to delay this update, we were affected by some very important issues. Working on fix and will try to push this out as fast as we can :).</p> <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>13:10:39</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time, to preform panel update with new features! More information can be found on our https://discord.gg/U5VuePpsEF.</p> ]]> Wed, 8 Oct 2025 12:00:00 +0000 https://voxihost.instatus.com/maintenance/cmgfq7p6803t210ny4r0qzkmo https://voxihost.instatus.com/maintenance/cmgfq7p6803t210ny4r0qzkmo RPKI, Connection issue Type: Incident Duration: 4 hours and 20 minutes Affected Components: Strona Główna, , VPS Panel, Node #1 (Germany/FRA), Inne → Sep 1, 16:35:31 GMT+0 - Identified - We have identified the connection issues they are connected to RPKI of the subnet we own. We are in contact with provider to solve it. Sep 1, 18:59:42 GMT+0 - Identified - Unfortunately, due to an error in IPXO’s new payment system, our subnet was temporarily removed, and as a result, the RPKI associated with our ASN was revoked. This has caused some providers not to update the propagation correctly yet, which explains the reachability issues with our ip-range. We are already working with IPXO to ensure full restoration as soon as possible. Compensation will be provided after the incident will be resolved! We sincerely apologize for the inconvenience. Daniel .M VoxiHost Team Sep 1, 19:32:01 GMT+0 - Monitoring - We believe the issue may be resolved, but we will continue to monitor the situation for a few more minutes. Daniel .M VoxiHost Team Sep 1, 20:55:55 GMT+0 - Resolved - We can confirm that this incident has been fully resolved. We will be providing compensation to all affected customers in the form of an additional day of service on their VPS servers. Thank you for your understanding. Daniel M. VoxiHost Team Type: Incident

Duration: 4 hours and 20 minutes

Affected Components: , , ,

<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>16:35:31</var> GMT+0</small><br><strong>Identified</strong> - We have identified the connection issues they are connected to RPKI of the subnet we own. We are in contact with provider to solve it..</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>18:59:42</var> GMT+0</small><br><strong>Identified</strong> - Unfortunately, due to an error in IPXO’s new payment system, our subnet was temporarily removed, and as a result, the RPKI associated with our ASN was revoked. This has caused some providers not to update the propagation correctly yet, which explains the reachability issues with our ip-range. We are already working with IPXO to ensure full restoration as soon as possible. Compensation will be provided after the incident will be resolved! We sincerely apologize for the inconvenience. Daniel .M VoxiHost Team.</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>19:32:01</var> GMT+0</small><br><strong>Monitoring</strong> - We believe the issue may be resolved, but we will continue to monitor the situation for a few more minutes. Daniel .M VoxiHost Team.</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>20:55:55</var> GMT+0</small><br><strong>Resolved</strong> - We can confirm that this incident has been fully resolved. We will be providing compensation to all affected customers in the form of an additional day of service on their VPS servers. Thank you for your understanding. Daniel M. VoxiHost Team.</p> ]]> Mon, 1 Sep 2025 16:35:31 +0000 https://voxihost.instatus.com/incident/cmf1cbqrm002my8l9heae6cil https://voxihost.instatus.com/incident/cmf1cbqrm002my8l9heae6cil Neoprotect, Maintenance Type: Maintenance Duration: 2 minutes Affected Components: Strona Główna, VPS Panel, Node #1 (Germany/FRA) Jul 21, 22:04:58 GMT+0 - Identified - Maintenance is now in progress. Jul 21, 22:00:00 GMT+0 - Identified - Neoprotect - Network <https://neoprotect.statuspage.io/incidents/cl7nqp9yfzjc> This will cause network issues, for 1-20min. Jul 21, 22:06:37 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 2 minutes

Affected Components: , ,

<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>22:04:58</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br><strong>Identified</strong> - Neoprotect - Network <https://neoprotect.statuspage.io/incidents/cl7nqp9yfzjc> This will cause network issues, for 1-20min..</p> <p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>22:06:37</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Mon, 21 Jul 2025 22:00:00 +0000 https://voxihost.instatus.com/maintenance/cmddnlten014113pmpnpun6b3 https://voxihost.instatus.com/maintenance/cmddnlten014113pmpnpun6b3 Firmware Update Type: Maintenance Duration: 5 hours Affected Components: Node #1 (Germany/FRA) Jun 9, 23:00:00 GMT+0 - Identified - Firmware Update in one of the network switches, it will cause "Network Interruption" Jun 9, 23:05:00 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 5 hours

Affected Components:

<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Identified</strong> - Firmware Update in one of the network switches, it will cause "Network Interruption".</p> <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>23:05:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Mon, 9 Jun 2025 23:05:00 +0000 https://voxihost.instatus.com/maintenance/cmc1u3gbp002ilvhbke3fr325 https://voxihost.instatus.com/maintenance/cmc1u3gbp002ilvhbke3fr325