HostVenom & WinterNode - Notice history

Notice history

View current status

Feb 2026

FEB24
GS003.FSN, MC.CHI25, MC.CHI27, MC.CHI28, MC.CHI29, MC.CHI30, MC.CHI31 Maintenance
CompletedMaintenance5 hours
  • CompletedFebruary 24, 2026 at 9:00 PMUTC
    Maintenance has completed successfully
  • In progressFebruary 24, 2026 at 4:00 PMUTC
    Maintenance is now in progress
  • PlannedFebruary 24, 2026 at 4:00 PMUTC

    We're performing scheduled OS maintenance and game servers may be unavailable during this window. The hostname/node names will also change during this process but no IP changes will occur.

    Other gameserver nodes will not be affected. Please check your Game Panel home page to see if your gameserver is affected - https://winternode.com/help/getting-started/accessing-the-game-control-panel/#finding-your-server

    If you have any questions before or during this maintenance period, please reach out to our support team @ https://winternode.com/support/ .

Degraded Service Performance - Miami Data Center
ResolvedDegraded performance2 hours 22 minutes
  • ResolvedUTC

    The network connectivity issue has been identified as a DDoS attack, which has now been successfully mitigated. Network performance and all related services have returned to normal operation.

    During the investigation, a cooling issue affecting gs103.mia.winternode.com was also identified. This matter is unrelated to the DDoS event. We will coordinate with the data center team to schedule a separate maintenance window to address the cooling concern.

    Customers are encouraged to subscribe to our status page and follow the gs103.mia component for updates regarding the upcoming maintenance schedule and completion details.

  • UpdateUTC

    We have received a response from our service provider. Based on their initial investigation, they believe the issue is related to cooling and have escalated the matter to the Data Center Team for further inspection and any necessary corrective action.

    We have requested additional details to better understand the situation. From our observations, the behavior appears to be network related, as none of the game servers were forcefully powered off as this incident is ongoing.

    We will continue to share more information as it comes available.

  • InvestigatingUTC

    Our automated monitoring has detected an issue affecting game servers at our Miami data center. We have ticketed our service provider for more information.

    More details will be shared as they become available.

FEB19
MC.CHI18, MC.CHI19, MC.CHI20, MC.CHI21, MC.CHI22, MC.CHI23, MC.CHI24 Maintenance
CompletedMaintenance2 hours 34 minutes
  • CompletedFebruary 19, 2026 at 6:34 PMUTC
    Maintenance has completed successfully.
  • In progressFebruary 19, 2026 at 4:00 PMUTC
    Maintenance is now in progress
  • PlannedFebruary 19, 2026 at 4:00 PMUTC

    We're performing scheduled OS maintenance and game servers may be unavailable during this window. The hostname/node names will also change during this process but no IP changes will occur.

    Other gameserver nodes will not be affected. Please check your Game Panel home page to see if your gameserver is affected - https://winternode.com/help/getting-started/accessing-the-game-control-panel/#finding-your-server

    If you have any questions before or during this maintenance period, please reach out to our support team @ https://winternode.com/support/ .

Jan 2026

gs101.lax Hardware Issue
ResolvedDegraded performance18 hours 5 minutes
  • ResolvedUTC

    The node is back online and accessible. Our provider completed hardware diagnostics and replaced the power supply unit. Customers can now start their servers back online. We are actively monitoring the node for stability and will open a new incident if further action is needed.

  • UpdateUTC

    gs101.lax will be powered off within the next few minutes to allow the emergency hardware check to begin. We will power off all game servers to ensure data integrity. This comprehensive test will ran overnight.

    Please subscribe to this incident to receive further updates - https://status.hostvenom.com/cmkyfkdm40cf5vqph57soirg5 .

  • IdentifiedUTC

    We're are scheduling EMERGENCY HARDWARE MAINTENANCE for gs101.lax to start at 2AM Eastern Time US on January 29th, 2026.

    A comprehensive hardware test will be conducted by our service provider during this time period to ensure this machine is stable for future activities. We expect this to take 4 hours to 6 hours.

  • InvestigatingUTC

    Our service provider has picked up our ticket and is actively working to diagnosis this issue.

    Game servers will not be accessible during this time. We will keep you updated on when customers will be able to start their services again.

  • MonitoringUTC

    We have reviewed the server console and have forwarded a copy of the displayed logs to our service provider.

    We have rebooted the node to allow customers to access their game servers and will await the response from the data center team.

  • InvestigatingUTC

    An automated alert has been triggered by our monitoring system and our team has been notified. We are currently investigating this incident.

`gs101.lax` network unreachable
ResolvedMajor outage3 hours 8 minutes
  • ResolvedUTC

    No immediate issues were noticed from the test conducted. We have restarted the machine and have confirmed services are online again.

    If you are still experiencing issues, please reach out to our support team - https://winternode.com/support .

  • IdentifiedUTC

    Management team members are actively investigating this incident, which appears to be a Kernal Panic from first glance. We will run a few tests to ensure hardware stability before releasing this back to customers.

  • InvestigatingUTC

    An automated alert has been triggered by our monitoring system and our team has been notified. We are currently investigating this incident.

JAN26
MC.CHI32 Maintenance
CompletedMaintenance3 hours
  • CompletedJanuary 26, 2026 at 8:00 PMUTC

    Maintenance has been completed successfully. Customers on mc.chi32.winternode.com have been migrated to gs121.chi.winternode.com respectively. and now you can start up your server and get back to gaming!

    If you were using the WinterNode database server, please make sure to update the database host accordingly to gs121.chi.winternode.com as shown in the Databases tab of the Control Panel.

    If you are experiencing any issues starting your server, please submit a ticket in our Discord Server.

  • In progressJanuary 26, 2026 at 5:00 PMUTC
    Maintenance is now in progress
  • PlannedJanuary 26, 2026 at 5:00 PMUTC

    We're performing scheduled maintenance during this window, and game servers may be unavailable at times.

Dec 2025

DEC30
MC.CHI10 & MC.CHI11 Node Replacement
CompletedMaintenance3 hours 25 minutes
  • CompletedDecember 30, 2025 at 8:25 PMUTC

    Maintenance has been completed successfully. Customers on mc.chi11.winternode.com have been migrated to gs120.chi.winternode.com respectively. and now you can start up your server and get back to gaming!

    If you used WinterNode provided subdomains or have setup your own personal domains, you will need to update your DNS records accordingly.

    If you were using the WinterNode database server, please make sure to update the database host accordingly to gs120.chi.winternode.com as shown in the Databases tab of the Control Panel.

    If you are experiencing any issues starting your server, please submit a ticket in our Discord Server.

  • UpdateDecember 30, 2025 at 7:07 PMUTC

    MC.CHI10 -> GS118.CHI has been completed successfully and you can now start up your server and get back to gaming!

    If you used WinterNode provided subdomains or have setup your own personal domains, you will need to update your DNS records accordingly.

    If you were using the WinterNode database server, please make sure to update the database host accordingly to gs118.chi.winternode.com as shown in the Databases tab of the Control Panel.


    The file transfer for MC.CHI11 has been completed and we will continue to work setting up and restoring access on the new machine.

  • In progressDecember 30, 2025 at 5:00 PMUTC
    Maintenance is now in progress
  • PlannedDecember 30, 2025 at 5:00 PMUTC

    We will be performing a node replacement for MC.CHI10 and MC.CHI11 as part of our ongoing effort to improve performance and deploy newer hardware.

    What's happening

    • Temporary shutdown: All game servers on MC.CHI10 and MC.CHI11 will be powered off during the maintenance window.

    • Panel access: The affected nodes may be temporarily unavailable in the Game Panel while work is underway.

    • IP addresses: Most services will keep the same IPs. If your service requires an IP change, we will notify you directly after the migration.

    • Database migration: Databases hosted on these nodes will be moved. If your database host changes, you will need to update your database server IP/hostname in your configs once maintenance is complete.

    • Data integrity: No data loss is expected.

    What you need to do after the window

    1. Start your server from the Game Panel.

    2. If you use databases, update your database connection details with the new host information.

    Want to move sooner?

    If you would like to opt in for an earlier migration, open a ticket in the WinterNode Discord (#support) and we can coordinate an earlier move for your service.

    If you have any questions, please reach out to our Support team.

Network Connectivity Issues with MC.LON5
ResolvedMajor outage21 hours 48 minutes
  • ResolvedUTC

    This incident has been resolved. We will create a new incident if necessary, however, changes have been made to better protect our Node IP.

    Please reach out over Discord or Client Area Tickets if you are experiencing any issues.

  • UpdateUTC

    We observed some servers were still having connectivity issues on mc.lon5 and have applied an additional fix.

    If you need any assistance with your server please reach out to our support team.

    We are continuing to monitor, but as this update everything should be online and functional.

  • UpdateUTC

    We saw another attack that impacted this box, and we have made an adjustment in discussion with our upstream provider. Panel server management should be restored again.
    We are continuing to monitor this node.

    If you would like to move to another node (at our other provider) to avoid this issue, we're happy to transfer you. Please open a ticket.

  • MonitoringUTC

    One of our IP addresses was temporarily unavailable due to a large external DDoS attack. Service has since been restored, and we are actively monitoring the situation to determine whether further action is needed.

    We are in contact with the provider and monitoring the situation. They have shared some options if attacks continue.

  • IdentifiedUTC

    Our service provider has booted our machine into rescue mode and the technician that looked into it was unable to resolve the issue. They have returned our machine back into the normal operating system without networking still.

    Our ticket has now been assigned to the network team with our service provider, although we might be waiting longer than normal for a reply as it is a specific team.

  • InvestigatingUTC

    We have rebooted the node at the suggestion of the service provider. This has not resolved the network issue. We have provided more information to the service provider to see if this is a configuration issue on their end.

  • IdentifiedUTC

    Our automated alerts have been triggered again and we are receiving support tickets regarding services on MC.LON5 being inaccessible.

    We have reviewed the server console and gameservers are still running, however, logging onto the server may be affected. We have re-opened our ticket with our service provider for more details and will post updates as they come in.

  • ResolvedUTC

    We've received an update from our upstream provider. Similar to the November Chicago Data Center incident, they reported high-volume "carpet bomb" DDoS activity that temporarily placed a large number of IPs into mitigation.

    We have not received any customer reports of disconnections. The provider advised that only ICMP (ping) may have been filtered during mitigation, which can trigger false positives on our uptime monitors. Regular TCP and UDP traffic was not impacted, and our IP addresses have now been removed from mitigation.

  • InvestigatingUTC

    We have received a few automated alerts regarding network connectivity issues to MC.LON5. We have confirmed with additional MTR tests that some clients might be unable to join servers hosted on MC.LON5.

    A ticket has been filed and we are awaiting further information from our service provider.

`gs101.lax` Unavailable [Machine]
ResolvedMajor outage4 hours 27 minutes
  • ResolvedUTC

    This incident has been resolved and all customers we have checked in with are reporting they are able to connect and manage their service.

  • MonitoringUTC

    We have restarted the network interface and confirmed that the IPs serving our game server customers are properly bound to the node. After starting multiple game servers, we can confirm that they are now coming online successfully.

    We ask all customers to start their servers and report any issues. We are moving this incident to the monitoring status and will be marked as resolved in one hour if no further problems are observed.

  • UpdateUTC

    A member of our management team has reviewed the server console and confirmed that the machine experienced a kernel panic. The server has been hard reset and has successfully rebooted to the operating system login screen.

    After attempting to start a game server, customers may encounter an error similar to:

    (HTTP code 500) server error - failed to set up container networking: driver failed programming external connectivity on endpoint ... (...): failed to bind host port for .../tcp: cannot assign requested address

    We are actively investigating this issue.

  • InvestigatingUTC

    An automated alert has been triggered by our monitoring system and our team has been notified. We are currently investigating this incident.

    The node has not responded after a restart. This has been escalated to the team to take a look at.

Previous

Dec 2025 to Feb 2026

Next