Is PloxHost Down Right Now? Check if there is a current outage ongoing.

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.

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.

This incident has been resolved.

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

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

This incident has been resolved.

We are currently investigating this issue.

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

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

We are currently investigating this issue.

This incident has been resolved.

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.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

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.

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.

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.

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.

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

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.

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.

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.

We are continuing to investigate this issue.

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

This incident has been resolved.

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

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

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

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

This incident has been resolved.

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

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

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.

SSL has been renewed and node is back online!

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

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

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

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.

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.

This incident has been resolved.

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

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 billing@plox.host and a ticket will be created that way.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue and will be back soon.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

We are aware that our game panel (panel.plox.host) is unreachable and displaying an error 500. Our team is already investigating the root cause and looking to deploy a fix ASAP. Servers should not be affected by this, only the panel.

Issue has been resolved.

Services should be coming back online, we are continuing to monitor this. There was an issue with one of our providers upstreams that caused the network connectivity issues.

The upstream we use in Dallas is currently suffering from a ddos attack that has caused some network connectivity issues for our Dallas location. We will be monitoring the issue and will provide additional updates when we receive them.

The upstream has finally figured out how to mitigate a ddos attack and it's back online.

The upstream has reported back the network should be recovering. We will keep this incident opened for the next couple hours just incase something comes up.

The Primary upstream that we use in Dallas is currently suffering from a DDoS attack that has caused the Network to become unstable. They are currently working on mitigating the attack and stabilizing the network. While the upstream mitigates the attack services will experience intermittent connection issues.

The Primary upstream that we use in Dallas is currently suffering from a DDoS attack that has caused the Network to become unstable. They are currently working on mitigating the attack and stabilizing the network.

The upstream has reported back the network should be recovering. We will keep this incident opened for the next couple hours just incase something comes up.

The Primary upstream that we use in Dallas is currently suffering from a DDoS attack that has caused the Network to become unstable. They are currently working on mitigating the attack and stabilizing the network.

Migration has been completed.

We are currently migrating our Support Site to another provider.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

The DDoS attack hitting the network has been mitigated and network is operational. If your still having issues please reach out to us: https://support.plox.host/en/tickets/create/step1

The DC has reported that traffic should be stabilizing. We will continue to monitor things and close out this incident in a few hours if no issues arise.

Our data center has identified the cause of the ongoing connection issues in Dallas: a DDOS attack is targeting multiple subnets within our data center. We are monitoring the situation and will keep you all updated here. While the DC mitigates this attack you will see intermittent connection issues.

Our data center has identified the cause of the ongoing connection issues in Dallas: a DDOS attack targeting several nodes within our data center. We are monitoring the situation and will keep you all updated here. While the DC mitigates this attack you will see intermittent connection issues.

Our data center has identified the cause of the ongoing connection issues in Dallas: a DDOS attack targeting several nodes within our data center. We are monitoring the situation and will keep you all updated here.

Network has fully recovered and have not seen any issues. Incident is considered resolved.

Things should be stabilized and we are continuing to monitor if you need help please reach out to us via support ticket. https://support.plox.host/en/tickets/create/step1

We are continuing to monitor for any further issues.

It appears that the DDoS is targeting several subnets. Our team is working diligently to mitigate the impact and protect our services.

Traffic is slowly recovering, affected servers are gradually coming back online. Our team continues to monitor the situation closely to ensure full restoration of services.

Our data center team has identified the cause of the ongoing connection issues in Dallas: a DDOS attack targeting several nodes within our data center. Traffic is slowly recovering.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

Power has been fully restored to the datacenter. We currently Monitoring the issue

Power is being slowly restored

Indications show there is a power outage in the facility. We've reached out and are awaiting status updates.

This incident has been resolved.

We are continuing to monitor for any further issues.

The support panel is now functioning properly. We were updating the support panel and did not anticipate any downtime, but it was caused by file permission issues. These issues have since been resolved.

Our support center is currently experiencing technical difficulties. We're aware of the issue and actively working on a fix. In the meantime, please reach out to support@plox.host for assistance. Thank you for your patience.

All OpenVZ services should be fully operational. The downtime was due to a bad kernel update from OpenVZ.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

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

We have identified the ongoing issue. Our engineering team is working on fixing the issue.

We are actively investigating a partial; outage on our US Dallas 2 OpenVZ VPS hosting node. We have received reports of OpenVZ servers that are currently offline and experiencing boot-up difficulties. Our team is diligently working on a resolution and we expect to deploy a fix promptly. We sincerely apologize for any inconvenience this may cause. Please be assured that all other VPS services remain fully operational; this issue is confined exclusively to OpenVZ servers hosted on the Dallas 2 node.

This incident has been resolved.

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

We have diagnosed a disk failing on NYC-KVM-02, we are working to arrange a part swap.

This incident has been resolved.

We are continuing to work on a fix for this issue.

We have identified a failed drive on the node and are working on restoring data on a new drive.

This incident has been resolved.

Amsterdam Budget Minecraft Server Migrations An automated email has been sent to all affected customers. Please note the following changes. - A select number of Budget Minecraft Hosting Servers located in Frankfurt, Germany will be migrated to our new infrastructure located in Amsterdam, The Netherlands. - All files will remain the same, including worlds, plugins, etc. - Your servers IP address will change, if you are using a PloxHost Subdomain, no action required. This new IP address has already been emailed to you. - The latency difference is very minor / none at all. We recommend that you read our full migration FAQ located at: https://help.plox.host/ams-migration/. Thank you. Please do not hesitate to reach out to our support team if you have any questions!

Power has been fully restored and repairs have been made. No outage.

Power still remains on backup generators as the datacenter is having troubles switching to the main. An engineer from the power company is on-site to resolve the problem.

Our datacenter in Amsterdam has lost main power feed. We remain on backup generators until the feed is restored. All services are online.

Appears to have been solved by our upstream. We apologize for any inconvenience- we will continue to monitor.

Our hosting provider OVH is having an outage which is effecting our billing panel operations. We will update soon.

We apologize for any inconvenience in which we have caused. The issue has been resolved. Thank you for your patience.

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

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We have implemented extra ddos protection measures towards the effected services. Our team is monitoring any continuous changes.

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

We are currently investigating this issue.

This incident has been resolved.

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

Our team is working to resolve targeted denial-of-service attacks towards our critical infrastructure. You may notice delays on our websites as our team works to resolve. Thank you for your patience.

Maintenance was resolved a little while ago. Downtime was short, and we will send a full report to customers via email shortly. Thank you for your patience regarding this downtime- the goal of this was to improve our network.

Work is now in progress

Within NYC Rack 01 we will be replacing fiber between our core switch. We expect 10 minutes of downtime as we need to reconfigure the disruption to this rack.

This incident has been resolved.

Routes via HE.Net will have issues until their routers are refreshed. All other routes are accessible/working fine. We are working with HE.net to resolve connectivity issues.

We are working to add additional redundancy and capacity in our Dallas DC. We will be running new fiber lines between racks and deploying a second router. Small amounts of packet loss may be expected temporarily.

This incident has been resolved.

We are seeing high latency across routes on HE.Net (Hurricane Electric) in all of our locations. This is an ISP issue, we have no control over high latency in this regard. We have reached out to HE for more information.

This incident has been resolved.

We have diagnosed the issue to be within R03 Dallas. Partial outages are in MC, VPS & Discord Bot Hosting. We are working to resolve the issue.

We are currently investigating this issue.

Due to a power issue EU MC nodes 50-56 were temporarily offline. We have solved the problem. Thank you for your patience.

Issue caused by upstream. We will post an RFO shortly.

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

This incident has been resolved.

We are working with Hurricane Electric (HE) to resolve the issue

Packets going through HE Ashburn location are being dropped. We are investigating the cause.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We have identified packet loss between Twelve99 ISP and our NYC network. We have contacted the ISP for more details. You may see issues between Hetzner and our NYC network.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Hetzner has notified us of a switch fault which affects our infra node in EU. Delays may be seen when running certain processes.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Our datacenter tech is working to resolve the issue with the node. Thank you for your patience.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.