RackNerd Outage History

Started Jul 09, 2026, 05:58 AM UTC· resolved Jul 09, 2026, 05:58 AM UTC

1. resolved Jul 09, 2026, 05:58 AM UTC

   We are aware that "FR102KVM" is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist. UPDATE: We are seeing a recurrence of the previous issues with "FR102KVM". Our team is investigating this further. UPDATE: This is now resolved again. We are keeping a close eye on this. If you experience any issues, please open a support ticket and we'll assist immediately. UPDATE: It appears that FR102KVM is experiencing intermittent issues again. Our engineers are performing additional diagnostic tests to identify the root cause and to get to the bottom of this. We sincerely apologise for the continued issues with this, and we will work to implement a permanent resolution ASAP. Thank you for your extended patience while we work on this. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 09, 2026, 02:10 AM UTC· resolved Jul 09, 2026, 02:10 AM UTC

1. resolved Jul 09, 2026, 02:10 AM UTC

   We are aware that SJ255KVM, SJ163KVM, SJ167KVM, and SJRYZEN100 are currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist. UPDATE: We are seeing a recurrence of the previous issues with SJ255KVM, SJ163KVM, SJ167KVM, and SJRYZEN100. Our team is investigating this further. UPDATE: The PDU on this rack appears to be failing. We are working on a solution with the remote hands team in San Jose. UPDATE: These nodes SJ255KVM, SJRYZEN100, SJ167KVM are now resolved again. We are keeping a close eye on this and still working on SJ163KVM. If you experience any issues, please open a support ticket, and we'll assist immediately. UPDATE: This has been resolved for the pending one "SJ163KVM" as well. All set now. If you experience any issues, please open a support ticket and we'll assist immediately.

Read the full incident report →

Started Jul 09, 2026, 02:10 AM UTC· resolved Jul 09, 2026, 02:10 AM UTC

1. resolved Jul 09, 2026, 02:10 AM UTC

   Our infrastructure team has been proactively and quickly responding to CVE-2026-53359 also known as "Januscape", which affects KVM-based virtualization environments and is not specific to RackNerd. Once the CVE became known, we promptly applied live mitigations across the majority of our KVM VPS hypervisors. This is not related to any known security incident or compromise affecting RackNerd or our customers. As an additional precaution, we will be rebooting a small number of host nodes where we cannot fully verify that the live mitigation was successfully applied. This is being done to ensure the appropriate kernel-level patches and mitigations are fully in place. Customers on impacted nodes may experience a brief VPS reboot, with expected downtime lasting less than 10 minutes. No customer action is required. Security remains our top priority, and we appreciate your understanding as we complete this proactive maintenance. UPDATE 9:30 PM PDT: Our infrastructure team has completed our response to CVE-2026-53359, also known as “Januscape.” At this time, we have verified that 100% of our KVM VPS fleet is protected against this CVE through either successfully applied live mitigations or completed host-node reboots where additional verification was required. For customers whose VPS experienced a brief reboot, this means your VPS was on a host node where we could not fully verify that the live mitigation had been successfully applied without a reboot. Out of an abundance of caution, that host node was rebooted to ensure the appropriate kernel-level patches and mitigations were fully in place. For customers whose VPS did not reboot, this means the required live/in-memory mitigation was successfully applied and verified on the underlying host node without requiring a reboot or service interruption. This was a proactive security response and was not related to any known security incident or compromise affecting RackNerd or our customers. No customer action is required. Security remains our top priority, and we sincerely appreciate your patience and understanding while our team completed this work.

Read the full incident report →

Started Jul 08, 2026, 10:29 PM UTC· resolved Jul 08, 2026, 10:29 PM UTC

1. resolved Jul 08, 2026, 10:29 PM UTC

   We are currently aware of an upstream software vendor issue affecting cPanel license validation, which may impact access to cPanel/WHM across some Shared Hosting, Reseller Hosting, and Managed Hosting environments. Affected users may see license-related errors when attempting to log in to cPanel/WHM, or may notice that manual license refresh attempts stall or timeout. At this time, this appears to be related to an ongoing issue with cPanel’s licensing servers and is not specific to RackNerd infrastructure. cPanel has publicly acknowledged the issue, and it is impacting license validation for all cPanel/WHM environments (not just RackNerd's). Websites, email services, databases, and the underlying servers themselves are expected to continue operating normally; the primary impact is temporary limited access to the cPanel/WHM interface. cPanel has publicly acknowledged the issue here: https://support.cpanel.net/hc/en-us/articles/41816676353943-cPanel-License-Update-Failures-July-8th-2026 We are actively monitoring the situation and will attempt license refreshes where needed once cPanel’s licensing systems are responding normally again. We appreciate your patience and understanding while this upstream issue is being reviewed. UPDATE: This upstream cPanel licensing issue appears to be getting resolved at this time. cPanel/WHM access is becoming available again, and affected users should now be able to log in normally. Our team will continue monitoring the situation and will perform any needed license refreshes where applicable. If you are still seeing a license-related error, please allow a bit of time and try again, as cPanel’s licensing systems may still be stabilizing. Thank you for your patience and understanding.

Read the full incident report →

Started Jul 08, 2026, 04:44 PM UTC· resolved Jul 08, 2026, 04:44 PM UTC

1. resolved Jul 08, 2026, 04:44 PM UTC

   We are aware that 7950XSJ300 is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 08, 2026, 07:01 AM UTC· resolved Jul 08, 2026, 07:01 AM UTC

1. resolved Jul 08, 2026, 07:01 AM UTC

   We are aware that SEA103KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 08, 2026, 02:53 AM UTC· resolved Jul 08, 2026, 02:53 AM UTC

1. resolved Jul 08, 2026, 02:53 AM UTC

   We are aware that 7950XSJ300 is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 07, 2026, 04:36 PM UTC· resolved Jul 07, 2026, 04:36 PM UTC

1. resolved Jul 07, 2026, 04:36 PM UTC

   We are aware that CHI180KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 07, 2026, 07:39 AM UTC· resolved Jul 07, 2026, 07:39 AM UTC

1. resolved Jul 07, 2026, 07:39 AM UTC

   We are aware that SEA103KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 06, 2026, 08:21 AM UTC· resolved Jul 06, 2026, 08:21 AM UTC

1. resolved Jul 06, 2026, 08:21 AM UTC

   We are aware that NYRN190KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 06, 2026, 07:28 AM UTC· resolved Jul 06, 2026, 07:28 AM UTC

1. resolved Jul 06, 2026, 07:28 AM UTC

   We are aware that NYRN290KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 06, 2026, 05:07 AM UTC· resolved Jul 06, 2026, 05:07 AM UTC

1. resolved Jul 06, 2026, 05:07 AM UTC

   We are aware that NYRN345KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 05, 2026, 07:55 PM UTC· resolved Jul 05, 2026, 07:55 PM UTC

1. resolved Jul 05, 2026, 07:55 PM UTC

   We are aware that CHI170KVM, CHI178KVM, CHI179KVM, CHI176KVM, CHI172KVM, CHI171KVM, CHI169KVM, CHI174KVM, CHI175KVM, CHI177KVM, CHI200KVM are currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: We sincerely apologize for the recurring issues affecting a portion of our Chicago location. The issue appears to be confined to a switch within one of our racks. Our team is actively working closely with onsite at this time to evaluate the best path forward, with the goal of ensuring this is permanently resolved - including the possibility of a full switch replacement if needed. To be clear, this issue is isolated to one specific rack within Chicago and is not impacting the entire location. We appreciate your patience and understanding while our team works through this. UPDATE 3:45 PM PDT: Services are now restored and operating normally. To minimize further downtime, we did not proceed with a full switch replacement at this time, as that would have resulted in a longer service interruption. Instead, we corrected the issue in place and have brought affected services back online. That said, there is still a possibility that the switch may be failing, so a replacement may be required in the near future. In the meantime, our team is proactively preparing and configuring a replacement switch in the background so we are ready to act if needed. If you are still experiencing any issues, please open a support ticket and we would be happy to assist. UPDATE: We are seeing a recurrence of the previous issues with the Chicago based host-nodes "CHI170KVM, CHI178KVM, CHI179KVM, CHI176KVM, CHI172KVM, CHI171KVM, CHI169KVM, CHI174KVM, CHI175KVM, CHI177KVM, CHI200KVM". Our team is investigating this further. UPDATE 3:10 AM PDT: We are continuing to work with our upstream provider as their Engineering team resolves this issue. We are continuing to monitor closely and will update this incident once there is meaningful progress to share. UPDATE 6:30 AM PDT: As the switch in the rack appears to now have completely failed, we are actively working with remote hands on getting a replacement switch in the rack and connections moved over. We will provide an update as soon as we have more information on this. UPDATE 9:02 AM PDT: The failed switch has now been fully removed from the rack and replaced with a brand-new switch. Services within this rack are now restored and operating normally. At this time, we expect connectivity to remain stable moving forward for the affected Chicago host nodes. To reiterate, this issue was isolated to one specific rack within our Chicago location and did not impact the entire facility. We sincerely apologize for the inconvenience caused by this incident and appreciate your patience while our team worked through the replacement.

Read the full incident report →

Started Jul 05, 2026, 03:03 AM UTC· resolved Jul 05, 2026, 03:03 AM UTC

1. resolved Jul 05, 2026, 03:03 AM UTC

   We are aware that DC03LA251KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 05, 2026, 12:54 AM UTC· resolved Jul 05, 2026, 12:54 AM UTC

1. resolved Jul 05, 2026, 12:54 AM UTC

   We are aware that ATL115KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 05, 2026, 12:46 AM UTC· resolved Jul 05, 2026, 12:46 AM UTC

1. resolved Jul 05, 2026, 12:46 AM UTC

   We are aware that NYRN374KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 04, 2026, 11:09 PM UTC· resolved Jul 04, 2026, 11:09 PM UTC

1. resolved Jul 04, 2026, 11:09 PM UTC

   We are aware that CHI170KVM, CHI178KVM, CHI179KVM, CHI176KVM, CHI172KVM, CHI171KVM, CHI169KVM, CHI174KVM, CHI175KVM, CHI177KVM, CHI200KVM are currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE 6:22 PM PDT: This is still actively being worked on by the Chicago onsite datacenter team. It appears to be an outage confined to a single rack and the issue is being investigated. We will provide additional updates once available. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 04, 2026, 11:55 AM UTC· resolved Jul 04, 2026, 11:55 AM UTC

1. resolved Jul 04, 2026, 11:55 AM UTC

   We are aware that LAXSSD7003DC03 is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 04, 2026, 11:39 AM UTC· resolved Jul 04, 2026, 11:39 AM UTC

1. resolved Jul 04, 2026, 11:39 AM UTC

   We are aware that DC03LA251KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 04, 2026, 10:06 AM UTC· resolved Jul 04, 2026, 10:06 AM UTC

1. resolved Jul 04, 2026, 10:06 AM UTC

   We are aware that SJ247KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 04, 2026, 02:24 AM UTC· resolved Jul 04, 2026, 02:24 AM UTC

1. resolved Jul 04, 2026, 02:24 AM UTC

   We are aware that NYRN273KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 04, 2026, 01:26 AM UTC· resolved Jul 04, 2026, 01:26 AM UTC

1. resolved Jul 04, 2026, 01:26 AM UTC

   We are aware that NYRN208KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 03, 2026, 07:51 PM UTC· resolved Jul 03, 2026, 07:51 PM UTC

1. resolved Jul 03, 2026, 07:51 PM UTC

   We are aware that DC03LA194KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 03, 2026, 04:09 PM UTC· resolved Jul 03, 2026, 04:09 PM UTC

1. resolved Jul 03, 2026, 04:09 PM UTC

   We are aware that there is currently a partial network outage in our New York datacenter location impacting some routes. Our network engineering team is currently looking into this further. We will have more information on this shortly. UPDATE: This is now resolved. If you are still experiencing any issues, please open a support ticket and we'd be happy to assist.

Read the full incident report →

Started Jul 03, 2026, 09:16 AM UTC· resolved Jul 03, 2026, 09:16 AM UTC

1. resolved Jul 03, 2026, 09:16 AM UTC

   We are aware that NYRN113KVM is currently experiencing connectivity issues. We are currently looking into this node further and will provide additional updates on this matter once we have more information. UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Read the full incident report →