PloxHost Outage History

Started Sep 01, 2026, 04:49 PM UTC· resolved Sep 01, 2026, 06:21 PM UTC

1. investigating Sep 01, 2026, 04:49 PM UTC

   We are currently investigating an issue causing the game panel to be unavailable. Game servers and Discord bots are not affected and remain operational. We will provide an update as soon as more information becomes available.

2. investigating Sep 01, 2026, 05:21 PM UTC

   This issue is affecting our support center, game panel, and dedicated control panel. No servers appear to be affected. Our team is still investigating the root cause for this issue.

3. identified Sep 01, 2026, 05:52 PM UTC

   We have identified the root cause for this issue, we are pushing a fix, and we expect for the services to be back soon.

4. monitoring Sep 01, 2026, 06:02 PM UTC

   Our game panel and Support site are working again. We will closely monitor the stability of the services.

5. resolved Sep 01, 2026, 06:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 18, 2026, 08:41 PM UTC· resolved Jul 19, 2026, 02:21 AM UTC

1. investigating Jul 18, 2026, 08:41 PM UTC

   We are receiving reports regarding performance and accessibility issues from customers hosted on node eu-finland-mc-bu78.ploxhost.com. Our team is actively investigating the root cause to get everything running smoothly again. We are on it, and we will post another update here as soon as we have more details to share. No other nodes or locations are affected. Thank you for your patience while we look into this.

2. investigating Jul 18, 2026, 08:44 PM UTC

   We have placed node eu-finland-mc-bu78.ploxhost.com into maintenance mode while our team works to resolve the ongoing issues. Players will be unable to connect to servers hosted on this node during this window. Your data is completely safe, and there is no risk of data loss or file corruption during this maintenance. We are actively working to get everything back online as quickly as possible and will post another update here as soon as we have a firm ETA. Thank you for your patience.

3. monitoring Jul 18, 2026, 08:48 PM UTC

   Maintenance mode has been disabled, and node eu-finland-mc-bu78.ploxhost.com is back online. All servers should now be accessible, and players can safely reconnect. Our team is closely monitoring the node's performance to ensure continued stability. Thank you again for your patience.

4. resolved Jul 19, 2026, 02:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 27, 2026, 09:53 PM UTC· resolved Jun 27, 2026, 10:18 PM UTC

1. investigating Jun 27, 2026, 09:53 PM UTC

   We are currently investigating this issue.

2. identified Jun 27, 2026, 10:00 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jun 27, 2026, 10:01 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jun 27, 2026, 10:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 03, 2026, 03:42 PM UTC· resolved Apr 03, 2026, 06:08 PM UTC

1. investigating Apr 03, 2026, 03:42 PM UTC

   We are currently investigating a service disruption affecting our client area at billing.plox.host. Our engineering team is currently diagnosing the root cause. This issue impacts our client area only. All active servers remain fully operational.

2. monitoring Apr 03, 2026, 04:08 PM UTC

   We have identified and resolved the underlying issue affecting the Billing Panel. We are currently monitoring the stability of the panel to ensure peak performance remains consistent. We will provide a final update once we are confident the service is fully stabilized. Customers can now access the panel and manage invoices without further issues.

3. resolved Apr 03, 2026, 06:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 31, 2025, 05:09 AM UTC· resolved Jan 02, 2026, 08:01 AM UTC

1. identified Dec 31, 2025, 05:09 AM UTC

   The issue has been identified and a fix is being implemented.

2. resolved Jan 02, 2026, 08:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 02, 2025, 03:52 AM UTC· resolved Nov 02, 2025, 09:32 PM UTC

1. investigating Nov 02, 2025, 03:52 AM UTC

   We are currently investigating this issue.

2. monitoring Nov 02, 2025, 05:48 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Nov 02, 2025, 09:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 01:40 PM UTC· resolved Oct 29, 2025, 01:48 PM UTC

1. investigating Oct 29, 2025, 01:40 PM UTC

   We are currently investigating this issue.

2. resolved Oct 29, 2025, 01:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 12, 2025, 08:10 PM UTC· resolved Oct 12, 2025, 08:53 PM UTC

1. investigating Oct 12, 2025, 08:10 PM UTC

   We are currently investigating this issue.

2. resolved Oct 12, 2025, 08:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 03, 2025, 11:47 AM UTC· resolved Oct 03, 2025, 11:55 AM UTC

1. investigating Oct 03, 2025, 11:47 AM UTC

   We are currently investigating this issue.

2. resolved Oct 03, 2025, 11:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 27, 2025, 01:45 PM UTC· resolved Sep 27, 2025, 04:26 PM UTC

1. investigating Sep 27, 2025, 01:45 PM UTC

   We're aware of some interruptions with our Registry service. We're investigating further and will provide more details soon.

2. monitoring Sep 27, 2025, 04:11 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 27, 2025, 04:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 06, 2025, 06:11 PM UTC· resolved Sep 06, 2025, 06:26 PM UTC

1. investigating Sep 06, 2025, 06:11 PM UTC

   We are currently investigating connectivity issues affecting some nodes in our Finland (EU) region. Our team is actively working to identify the cause and will provide updates as soon as possible.

2. resolved Sep 06, 2025, 06:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 12, 2025, 07:54 PM UTC· resolved Aug 15, 2025, 07:21 PM UTC

1. identified Aug 12, 2025, 07:54 PM UTC

   The issue has been identified and a fix is being implemented.

2. monitoring Aug 13, 2025, 07:28 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 15, 2025, 07:21 PM UTC

   Our registry system, which manages all Minecraft servers, is now fully operational. The downtime was caused by an issue with a third-party provider that resulted in the registry going offline, affecting multiple servers. We have since rebuilt the registry on new infrastructure to prevent similar disruptions in the future and have implemented redundancy to ensure this does not happen again. We sincerely apologize for the inconvenience caused and appreciate your patience while we worked to restore services.

Read the full incident report →

Started Jul 25, 2025, 03:36 PM UTC· resolved Aug 12, 2025, 01:59 AM UTC

1. investigating Jul 25, 2025, 03:36 PM UTC

   Our data center is currently investigating issues with some of our nodes in Dallas. Apologies for the inconvenience caused.

2. monitoring Jul 26, 2025, 06:39 AM UTC

   A fix has been implemented and we are monitoring the results.

3. identified Jul 30, 2025, 08:59 PM UTC

   The issue has been identified and a fix is being implemented. We will update you when everything is back to working as intended.

4. resolved Aug 12, 2025, 01:59 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 02, 2025, 06:16 AM UTC· resolved Jul 25, 2025, 05:14 PM UTC

1. investigating Jul 02, 2025, 06:16 AM UTC

   We are aware that our game panel is returning a 502 error message when trying to access it. Our team is investigating the cause of this issue, and we will update you once we have more information. We apologize for the inconvenience.

2. monitoring Jul 03, 2025, 04:38 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jul 25, 2025, 05:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2025, 11:01 PM UTC· resolved Jul 25, 2025, 05:15 PM UTC

1. investigating Jul 01, 2025, 11:01 PM UTC

   We’re currently experiencing an issue where servers are not being created automatically after purchase. Our team is actively investigating and working on a fix. If you’ve recently made a purchase and haven’t received your server, please reach out to us, and we’ll assist you promptly. Thank you for your patience.

2. monitoring Jul 03, 2025, 04:39 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jul 25, 2025, 05:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2025, 11:29 PM UTC· resolved May 10, 2025, 11:27 PM UTC

1. identified May 07, 2025, 11:29 PM UTC

   Our team is aware of the recent downtime on our budget Minecraft node 22 and is currently working to bring the node back up.

2. monitoring May 10, 2025, 04:02 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved May 10, 2025, 11:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 29, 2025, 11:37 PM UTC· resolved Apr 30, 2025, 12:11 AM UTC

1. investigating Apr 29, 2025, 11:37 PM UTC

   We are currently investigating this issue.

2. resolved Apr 30, 2025, 12:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 26, 2025, 07:31 PM UTC· resolved Apr 26, 2025, 11:11 PM UTC

1. investigating Apr 26, 2025, 07:31 PM UTC

   We are currently investigating this issue.

2. monitoring Apr 26, 2025, 07:44 PM UTC

   This is related to an on-going outage at the DC (Datacenter).

3. resolved Apr 26, 2025, 11:11 PM UTC

   The DC reported that the "he rpd daemon crashed" stuff has stabilized and we are closing this incident

Read the full incident report →

Started Apr 23, 2025, 01:54 AM UTC· resolved Apr 23, 2025, 10:23 AM UTC

1. identified Apr 23, 2025, 01:54 AM UTC

   The issue has been identified and a fix is being implemented.

2. resolved Apr 23, 2025, 10:23 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 23, 2025, 09:19 PM UTC· resolved Mar 24, 2025, 01:49 AM UTC

1. identified Mar 23, 2025, 09:19 PM UTC

   We are working on migrating our emails to another provider. Once we get this fixed things should be back to normal.

2. identified Mar 24, 2025, 12:23 AM UTC

   Most of our important support emails are now working as intended. We will post another update once all of our emails are back to normal

3. resolved Mar 24, 2025, 01:49 AM UTC

   All emails should be working now. apologies if you have encountered issues submitting tickets.

Read the full incident report →

Started Mar 13, 2025, 10:24 PM UTC· resolved Mar 15, 2025, 09:28 PM UTC

1. investigating Mar 13, 2025, 10:24 PM UTC

   We are currently investigating an issue with one of EU extreme node that's having communication issues with the panel. We will updated the status page as more information is available.

2. identified Mar 14, 2025, 01:33 AM UTC

   We identified the issue with the communication between the node and panel. The IPtable broke. We are currently fixing it.

3. monitoring Mar 14, 2025, 01:34 AM UTC

   IPtables has been fixed and we are currently monitoring the node to ensure no errors appear for 24 hours.

4. resolved Mar 15, 2025, 09:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 08, 2025, 09:15 PM UTC· resolved Mar 08, 2025, 09:40 PM UTC

1. investigating Mar 08, 2025, 09:15 PM UTC

   We are currently investigating the cause of the server being offline.

2. identified Mar 08, 2025, 09:40 PM UTC

   SSL has expired on the node, currently in the process of renewing it.

3. resolved Mar 08, 2025, 09:40 PM UTC

   SSL has been renewed and node is back online!

Read the full incident report →

Started Mar 06, 2025, 08:04 PM UTC· resolved Mar 07, 2025, 03:40 PM UTC

1. investigating Mar 06, 2025, 08:04 PM UTC

   We are currently investigating what is causing the Minecraft servers to fail to start. I will update the statue page once more information is available.

2. monitoring Mar 07, 2025, 12:57 AM UTC

   The issue was identified and currently being monitored to ensure no other issues arises. The issue identified was due to our CDN going offline for a short period of time due to networking issues.

3. resolved Mar 07, 2025, 03:40 PM UTC

   The issue with CDN has been resolved, and no further outages have been reported.

Read the full incident report →

Started Feb 20, 2025, 07:11 PM UTC· resolved Apr 23, 2025, 10:23 AM UTC

1. investigating Feb 20, 2025, 07:11 PM UTC

   We are aware of the panel and servers being down. We are currently investigating the issue and will post updated as we learn more.

2. investigating Feb 20, 2025, 09:16 PM UTC

   We are continuing to investigate this issue.

3. identified Feb 21, 2025, 01:20 AM UTC

   Earlier today we received a notification from our VPS panel provider (Virtualizor) that they suffered a security breach. In response to this, we have been working on reinstalling and mitigating any possible way that client data could be accessed in regards to this. As soon as we found out about this, we notified our operations team and we have been in a meeting all day in order to make sure that we are able to resolve this as fast as possible. It doesn't seem like any customer data has been accessed by this security exploit. We will also be in contact with the vps software provider (Virtualizor) to see what they will be doing to prevent these exploits from happening again in the future.

4. identified Feb 21, 2025, 03:03 PM UTC

   We are still continuing to work on getting things back online we apologize for the inconvenience. Once we have more info will share it with you all.

5. identified Feb 22, 2025, 06:04 PM UTC

   We are still in the process of restoring our VPS system. A new master node has been created that is completely separate from our slave node. We are currently in the process of restoring the old master node, which involves reinstalling the OS, installing the slave program, and restoring the data from our backup. It's been a bumpy road throughout this whole process. Rest assured, this is priority number one for us and we will work through the weekend to resolve this. Compensation will be provided once the services are restored.

6. identified Feb 23, 2025, 01:00 AM UTC

   Hi everyone first and foremost we are sorry for all these issues. Our teams are working very hard to getting things back up and running. Once everything is up and running it's gonna take 48 hours to get everything restored. Unfortunately, This will be the longest part of this. But, We are working hard and this is the highest priority

7. identified Feb 23, 2025, 05:04 PM UTC

   Time for a morning update! As of right now we do have the panel online. However, There still needs to be a lot of configuration that needs to be done. Once the configuration is done then we can start the restoring process. Unfortunately, as mentioned in the previous update restoring will the longest processes as we can't restore multiple servers at a time and it has to be done one at the time. I also just want to remind everyone there will be SLA compensation for these issues.

8. identified Feb 25, 2025, 03:43 AM UTC

   We have another update regarding this ongoing outage: The original Virtualizor issue affected our Discord bot database, which is why many bots are still offline. Right now, we are in the process of restoring the database, but this is a time-consuming task, and our system administrators are working as fast as possible to get everything back online. We are also still working on bringing all VPS nodes back up. Some have already been restored, but there are still a few that remain offline. This has been a complex issue, and we know it's been frustrating. We appreciate everyone's patience as we work through it. We want to reassure everyone that SLA compensation will be provided once everything is fully restored. This outage is being treated with the highest priority, but we also want to ensure the process is done carefully to avoid any data corruption. We will keep updating you over the coming hours.

9. identified Feb 25, 2025, 07:36 PM UTC

   The Discord bot database has been restored, and we are now working on getting the network online. We appreciate your patience and will provide another update once we have more progress.

10. monitoring Feb 25, 2025, 08:02 PM UTC

    The Discord bot database has been restored, and the network is now online. We have completed initial testing on the node, and everything appears to be stable. At this point, we are moving this issue to monitoring to ensure continued stability. Our team will remain on high alert, and if any further issues arise, we will address them immediately. With the database now restored, we are shifting focus to restoring VPS services. This process is now underway, and we will provide further updates as progress is made. Thank you for your patience throughout this process. SLA compensation will still be provided once everything is fully confirmed as resolved.

11. monitoring Feb 26, 2025, 01:59 AM UTC

    We are continuing to monitor for any further issues.

12. monitoring Feb 26, 2025, 02:00 AM UTC

    We are continuing to monitor for any further issues.

13. monitoring Feb 27, 2025, 06:39 PM UTC

    We have most of our VPS infrastructure back online and are still working on restoring VPS services and adjusting a few other things. We will continue to keep this active until things are back to normal.

14. resolved Apr 23, 2025, 10:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Feb 17, 2025, 01:40 PM UTC· resolved Feb 18, 2025, 12:12 PM UTC

1. investigating Feb 17, 2025, 01:40 PM UTC

   We are currently investigating this issue.

2. investigating Feb 17, 2025, 05:11 PM UTC

   We are continuing to investigate this issue.

3. investigating Feb 17, 2025, 08:52 PM UTC

   We are still looking into this. We have reached out to our vendor.

4. investigating Feb 18, 2025, 05:19 AM UTC

   We are still waiting to hear back from our vendor. if you have any billing issues please submit a ticket: https://support.plox.host/en/tickets/create/step1 and we will assist as best we can. If you can't submit a ticket from the link above send an email to [email protected] and a ticket will be created that way.

5. monitoring Feb 18, 2025, 09:49 AM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Feb 18, 2025, 12:12 PM UTC

   This incident has been resolved.

Read the full incident report →