RackNerd Outage History

Started Jun 15, 2026, 01:57 PM UTC· resolved Jun 15, 2026, 01:57 PM UTC

1. resolved Jun 15, 2026, 01:57 PM UTC

   As previously communicated to affected customers via email, the following nodes will be undergoing a scheduled maintenance window shortly: ASH118KVM, 7950XASH107, 7950XASH105, 7950XASH103, 7950XASH102, ASH114KVM, ASH111KVM, ASH107KVM, ASH119KVM, ASH106KVM, ASH109KVM and ASH113KVM Our team will be closely monitoring throughout this process, and will work closely with the on-site datacenter team to minimize disruption. We will update this status incident once the maintenance window is fully completed. Update : This is now completed for all the scheduled host nodes except the following: 7950XASH107, ASH119KVM, and ASH109KVM. Thank you for your extended patience while we work on this. Update : The maintenance has been completed for ASH119KVM as well. We will update this status incident once the maintenance window is fully completed for the rest of two host-nodes " 7950XASH107" ASH109KVM 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 Jun 15, 2026, 02:26 AM UTC· resolved Jun 15, 2026, 02:26 AM UTC

1. resolved Jun 15, 2026, 02:26 AM UTC

   We are aware that 7950XASH102 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 Jun 14, 2026, 10:18 PM UTC· resolved Jun 14, 2026, 10:18 PM UTC

1. resolved Jun 14, 2026, 10:18 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 Jun 14, 2026, 12:10 PM UTC· resolved Jun 14, 2026, 12:10 PM UTC

1. resolved Jun 14, 2026, 12:10 PM UTC

   We are aware that NYRYZEN104 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 NYRYZEN104. 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.

Read the full incident report →

Started Jun 14, 2026, 10:12 AM UTC· resolved Jun 14, 2026, 10:12 AM UTC

1. resolved Jun 14, 2026, 10:12 AM UTC

   We are aware that SEA137KVM 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 Jun 13, 2026, 06:47 PM UTC· resolved Jun 13, 2026, 06:47 PM UTC

1. resolved Jun 13, 2026, 06:47 PM 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 Jun 13, 2026, 02:30 PM UTC· resolved Jun 13, 2026, 02:30 PM UTC

1. resolved Jun 13, 2026, 02:30 PM UTC

   We are aware that DAL185KVM, DALRYZEN103, DALRYZEN101, DAL107KVM, DAL135KVM, DALRYZEN100 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.

Read the full incident report →

Started Jun 13, 2026, 02:19 PM UTC· resolved Jun 13, 2026, 02:19 PM UTC

1. resolved Jun 13, 2026, 02:19 PM UTC

   We are aware that DAL102KVM 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 Jun 12, 2026, 11:47 PM UTC· resolved Jun 12, 2026, 11:47 PM UTC

1. resolved Jun 12, 2026, 11:47 PM UTC

   We are aware that DC03LA179KVM 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 Jun 12, 2026, 08:18 PM UTC· resolved Jun 12, 2026, 08:18 PM UTC

1. resolved Jun 12, 2026, 08:18 PM UTC

   We are aware that CHI108KVM, CHI118KVM, and CHI128KVM 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.

Read the full incident report →

Started Jun 12, 2026, 07:50 PM UTC· resolved Jun 12, 2026, 07:50 PM UTC

1. resolved Jun 12, 2026, 07:50 PM 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 Jun 12, 2026, 07:10 PM UTC· resolved Jun 12, 2026, 07:10 PM UTC

1. resolved Jun 12, 2026, 07:10 PM UTC

   We are aware that SJ264KVM 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 Jun 12, 2026, 11:34 AM UTC· resolved Jun 12, 2026, 11:34 AM UTC

1. resolved Jun 12, 2026, 11:34 AM UTC

   We are aware that SEA124KVM 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 Jun 12, 2026, 07:40 AM UTC· resolved Jun 12, 2026, 07:40 AM UTC

1. resolved Jun 12, 2026, 07:40 AM UTC

   We are aware that NYRN227KVM,NYRN229KVM,NYRN239KVM,NYRN237KVM 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.

Read the full incident report →

Started Jun 12, 2026, 05:39 AM UTC· resolved Jun 12, 2026, 05:39 AM UTC

1. resolved Jun 12, 2026, 05:39 AM UTC

   We are aware that SJ126KVM 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 Jun 12, 2026, 05:38 AM UTC· resolved Jun 12, 2026, 05:38 AM UTC

1. resolved Jun 12, 2026, 05:38 AM UTC

   We have received a high temperature alert in our internal monitoring for node NYRN221KVM (one of our KVM VPS host nodes in New York). Please note that this particular matter is unrelated to the earlier broader New York network incident which is now resolved. Our on-site datacenter team is now inspecting this host node physically, and will be replacing the cooling fans on this machine as necessary in order to resolve this. We will provide additional updates in this status incident once resolved. 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 Jun 11, 2026, 02:41 PM UTC· resolved Jun 11, 2026, 02:41 PM UTC

1. resolved Jun 11, 2026, 02:41 PM UTC

   We are aware that SJ155KVM 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 Jun 11, 2026, 04:59 AM UTC· resolved Jun 11, 2026, 04:59 AM UTC

1. resolved Jun 11, 2026, 04:59 AM UTC

   We are aware that SJ214KVM 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 Jun 11, 2026, 04:23 AM UTC· resolved Jun 11, 2026, 04:23 AM UTC

1. resolved Jun 11, 2026, 04:23 AM UTC

   We are aware that DC03LA122KVM 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 Jun 10, 2026, 10:27 PM UTC· resolved Jun 10, 2026, 10:27 PM UTC

1. resolved Jun 10, 2026, 10:27 PM UTC

   We are currently investigating recent reports from customers experiencing higher than usual latency, packet loss, and/or intermittent connectivity when traversing certain network routes in our New York datacenter region. Our team has performed a thorough review of our infrastructure side, and at this time we have not found any evidence of any hardware or software issues within RackNerd-operated infrastructure. Based on our findings so far, this appears to be route-specific and may involve upstream network paths outside of our direct infrastructure, or potentially a core distribution router issue upstream at the datacenter. As such, we have escalated this matter to our upstream network providers for further investigation and review. We will continue to closely monitor the situation and work with our upstream providers toward resolution. Further updates will be posted here as more information becomes available. Thank you for your patience and understanding. UPDATE: Our upstream has acknowledged our report and confirmed the issue, and this is being looked into by their Engineering team. We will provide additional updates as soon as we find out more details. UPDATE 6:39 PM PDT: We are seeing improvement and from what we can see, progress is being made, though we are awaiting final confirmation from upstream before calling this resolved, as we believe they may still be actively working on addressing this issue. We will provide additional updates once available -- until this incident is marked as resolved you may experience intermittent connectivity or degraded network performance. UPDATE 8:00 PM PDT: Our upstream provider’s Engineering team is still actively investigating and working on the issue. While we have observed periods of improvement, we are not yet ready to mark this incident as resolved, as some customers may still experience intermittent connectivity, packet loss, or higher than usual latency depending on the network route being taken. We are continuing to monitor this closely and remain in communication with our upstream provider. We will post another update once we have additional information or confirmation that the issue has been fully resolved. Thank you again for your continued patience and understanding. UPDATE 10:00 PM PDT: Our upstream provider’s Engineering team remains actively engaged on this issue. At this time, we are continuing to see symptoms in some cases, meaning the impact may vary depending on where customers are connecting from, the network path being taken, and the specific destination/source involved. While there have been periods of improvement throughout the evening, we are not yet comfortable marking this incident as resolved until we see sustained stability and/or receive final confirmation from upstream. We understand how frustrating intermittent network issues can be, especially when they are inconsistent or route-specific in nature. Please know that our team is continuing to monitor the situation closely from our side, and we are continuing to follow up with upstream for further updates and resolution progress. Until this incident is marked as resolved, customers in the New York region may continue to experience intermittent packet loss, elevated latency, or connectivity issues depending on routing. We will provide another update as soon as we have meaningful new information to share, or once stability has been fully confirmed. Thank you again for your continued patience. UPDATE 12:05 AM PDT: Our upstream provider is still actively working on this issue. The impact remains intermittent and route-specific, so some customers may see normal connectivity while others may continue to experience packet loss or higher latency depending on the route being taken. We are continuing to monitor from our side and will post another update once we have more information or confirmation of sustained stability. UPDATE 2:28 AM PDT: We are continuing to work with our upstream provider as their Engineering team investigates this issue. At this time, symptoms may still vary depending on source location and network path. We do not want to prematurely mark this incident as resolved until stability has been confirmed. Further updates will be posted as more information becomes available. UPDATE 4:56 AM PDT: This issue remains under active investigation with our upstream provider. We have observed additional periods of improvement, but intermittent packet loss or elevated latency may still occur for some customers depending on routing. We are continuing to monitor closely and will update this incident once there is meaningful progress to share. UPDATE 7:42 AM PDT: Our upstream provider's Engineering team remains engaged, and we are continuing to monitor the situation closely from our side. The issue continues to appear intermittent in nature. Until we have confirmation that the issue is fully resolved, this incident will remain open. We appreciate your continued patience. UPDATE 1:30 PM PDT: Our upstream provider’s Engineering team is continuing to investigate and monitor this issue. At this stage, we are seeing that the majority of customers with services hosted in our New York datacenter should no longer be impacted, and the remaining symptoms appear to be limited to certain IP ranges. We are continuing to work with upstream to better understand the remaining scope and ensure the issue is fully stabilized before marking this incident as resolved. We will share additional information as soon as it becomes available. Thank you again for your continued patience and understanding. UPDATE 10:00 PM PDT: At this time, this issue has stabilized, and we are closing this incident out. Our team will continue to keep a close eye on the New York network, and if there are any additional updates to share regarding this matter, we will create a new status incident as needed. We sincerely appreciate everyone’s patience and understanding while our team worked with upstream toward resolution.

Read the full incident report →

Started Jun 10, 2026, 09:32 PM UTC· resolved Jun 10, 2026, 09:32 PM UTC

1. resolved Jun 10, 2026, 09:32 PM UTC

   We are aware that NYRN181KVM 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: Further updates on this matter will be shared on this status incident link instead: https://status.racknerd.com/incident/4127

Read the full incident report →

Started Jun 10, 2026, 08:49 PM UTC· resolved Jun 10, 2026, 08:49 PM UTC

1. resolved Jun 10, 2026, 08:49 PM UTC

   We are aware that DC03LA178KVM 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 Jun 10, 2026, 08:41 PM UTC· resolved Jun 10, 2026, 08:41 PM UTC

1. resolved Jun 10, 2026, 08:41 PM UTC

   We are aware that NYRN011KVM 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: Further updates on this matter will be shared on this status incident link instead: https://status.racknerd.com/incident/4127

Read the full incident report →

Started Jun 10, 2026, 06:57 PM UTC· resolved Jun 10, 2026, 06:57 PM UTC

1. resolved Jun 10, 2026, 06:57 PM UTC

   We are aware that SJ192KVM 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 Jun 10, 2026, 04:45 PM UTC· resolved Jun 10, 2026, 04:45 PM UTC

1. resolved Jun 10, 2026, 04:45 PM UTC

   We have identified the recent recurring reboot/stability issues affecting the NYRN315KVM host node as being related to a faulty DIMM/RAM module. Our datacenter team will be replacing the affected memory module shortly. VPS services hosted on this node may experience temporary downtime or brief interruptions while the hardware replacement is completed and the node is brought back online. We will continue monitoring the node closely after the replacement is complete to ensure stability has been fully restored. Further updates will be provided as more information becomes 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 →