RackNerd Outage History

Started May 29, 2026, 01:10 AM UTC· resolved May 29, 2026, 01:10 AM UTC

1. resolved May 29, 2026, 01:10 AM UTC

   We are aware that NYRN114KVM 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 May 28, 2026, 03:24 PM UTC· resolved May 28, 2026, 03:24 PM UTC

1. resolved May 28, 2026, 03:24 PM UTC

   We are aware that DC03LA182KVM 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 May 28, 2026, 12:34 PM UTC· resolved May 28, 2026, 12:34 PM UTC

1. resolved May 28, 2026, 12:34 PM UTC

   We are aware that DC03LA186KVM 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 May 28, 2026, 03:56 AM UTC· resolved May 28, 2026, 03:56 AM UTC

1. resolved May 28, 2026, 03:56 AM UTC

   We are aware that NYRN115KVM 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 May 28, 2026, 02:30 AM UTC· resolved May 28, 2026, 08:10 AM UTC

1. resolved May 28, 2026, 02:30 AM UTC

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

2. resolved May 28, 2026, 08:10 AM UTC

   We are aware that DC03LA182KVM 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 May 27, 2026, 06:29 AM UTC· resolved May 27, 2026, 06:29 AM UTC

1. resolved May 27, 2026, 06:29 AM 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 May 26, 2026, 06:24 PM UTC· resolved May 26, 2026, 06:24 PM UTC

1. resolved May 26, 2026, 06:24 PM UTC

   We are aware that SEA113KVM 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 May 26, 2026, 06:02 PM UTC· resolved May 26, 2026, 06:02 PM UTC

1. resolved May 26, 2026, 06:02 PM UTC

   We are aware that SEA105KVM 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 May 26, 2026, 04:14 PM UTC· resolved May 26, 2026, 04:14 PM UTC

1. resolved May 26, 2026, 04:14 PM UTC

   We will be beginning the third batch of our Los Angeles DC-02 to Los Angeles DC-03 physical migration project today. Today's migration batch will begin at approximately 9:45 AM PDT. If your service is included in this specific batch, you would have already received a direct email notification from us specifically mentioning "Tuesday, May 26" in both the email subject and body, along with the exact service(s) impacted. As part of this maintenance, affected services will be physically migrated from our Los Angeles DC-02 facility to our Los Angeles DC-03 facility. This process involves powering down the affected hardware, physically transporting it to the new facility, re-racking it, reconnecting network/power, and bringing services back online. Please note that this maintenance only applies to customers who received a direct email notification for the Tuesday, May 26 migration batch. If you did not receive an email mentioning this date and your specific affected service, your service is not part of this batch. We appreciate your patience and understanding as we continue working through this relocation project. Our team will be actively monitoring the process and will provide additional updates on this status incident as the migration progresses. UPDATE 3:10 PM PDT: Services are beginning to come online at the new facility as today's migration batch continues progressing. Some customers may already be seeing their services restored at this time. Once your specific VPS has been brought back online, you will receive a separate email notification from us with a subject line prefixed with "[RackNerd]..." confirming completion for your service. Our team is continuing to work through the remaining systems in this batch, and we greatly appreciate your patience. UPDATE 4:40 PM PDT: We are now down to the final stretch of today’s Los Angeles DC-02 to Los Angeles DC-03 migration batch, with less than a handful of servers remaining. At this stage, our team is actively working through the remaining servers that did not automatically power back on normally and/or did not boot as expected following the physical relocation. These systems are being reviewed and addressed individually. We understand some affected customers are still waiting for their services to be restored, and we sincerely appreciate your continued patience. Our team is continuing to work through the remaining items as quickly and carefully as possible, and we will provide another update as additional progress is made. UPDATE 8:10 PM PDT: All affected services included in this batch have been brought back online at the new facility. Customers whose services were part of today’s migration should have also received a separate email notification from us with a subject line prefixed with “[RackNerd]...” confirming completion for their specific service. We sincerely appreciate our customers’ patience and understanding throughout today’s maintenance window.

Read the full incident report →

Started May 26, 2026, 07:13 AM UTC· resolved May 26, 2026, 07:13 AM UTC

1. resolved May 26, 2026, 07:13 AM UTC

   We are aware that DC03LA225KVM 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 May 26, 2026, 05:36 AM UTC· resolved May 26, 2026, 05:36 AM UTC

1. resolved May 26, 2026, 05:36 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 May 25, 2026, 07:10 PM UTC· resolved May 25, 2026, 07:10 PM UTC

1. resolved May 25, 2026, 07:10 PM UTC

   We are aware that DAL108KVM 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 May 25, 2026, 11:49 AM UTC· resolved May 25, 2026, 11:49 AM UTC

1. resolved May 25, 2026, 11:49 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 →

Started May 25, 2026, 11:28 AM UTC· resolved May 25, 2026, 11:28 AM UTC

1. resolved May 25, 2026, 11:28 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 May 25, 2026, 10:56 AM UTC· resolved May 25, 2026, 10:56 AM UTC

1. resolved May 25, 2026, 10:56 AM UTC

   We are aware that DC03LA182KVM 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 May 24, 2026, 01:13 AM UTC· resolved May 24, 2026, 01:13 AM UTC

1. resolved May 24, 2026, 01:13 AM UTC

   We are aware that DC03LA182KVM 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 May 23, 2026, 10:10 PM UTC· resolved May 23, 2026, 10:10 PM UTC

1. resolved May 23, 2026, 10:10 PM UTC

   We are aware that LAXSSD104DC03 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 May 23, 2026, 12:18 PM UTC· resolved May 23, 2026, 12:18 PM UTC

1. resolved May 23, 2026, 12:18 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 May 23, 2026, 12:03 PM UTC· resolved May 23, 2026, 12:03 PM UTC

1. resolved May 23, 2026, 12:03 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 May 23, 2026, 06:05 AM UTC· resolved May 23, 2026, 06:05 AM UTC

1. resolved May 23, 2026, 06:05 AM UTC

   We are aware that LAXSSD6016DC03 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 May 22, 2026, 01:35 PM UTC· resolved May 22, 2026, 01:35 PM UTC

1. resolved May 22, 2026, 01:35 PM UTC

   We will be beginning the second batch of our Los Angeles DC-02 to Los Angeles DC-03 physical migration project today. If your service is included in this specific batch, you would have already received a direct email notification from us specifically mentioning "Friday, May 22" in both the email subject and body, along with the exact service(s) impacted. As part of this maintenance, affected services will be physically migrated from our Los Angeles DC-02 facility to our Los Angeles DC-03 facility. This process involves powering down the affected hardware, physically transporting it to the new facility, re-racking it, reconnecting network/power, and bringing services back online. Please note that this maintenance only applies to customers who received a direct email notification for the Friday, May 22 migration batch. If you did not receive an email mentioning this date and your specific affected service, your service is not part of this batch. We appreciate your patience and understanding as we continue working through this relocation project. Our team will be actively monitoring the process and will provide additional updates on this status incident as the migration progresses. UPDATE 11:42 AM PDT: Work is currently in progress at the existing facility, and the affected equipment is being prepared for relocation as part of today’s migration batch. At this time, everything is moving forward as expected. We will continue to monitor the process closely and share additional updates as they become available. UPDATE 1:50 PM PDT: Services are beginning to come online at the new facility as today's migration batch continues progressing. Some customers may already be seeing their services restored at this time. Once your specific VPS has been brought back online, you will receive a separate email notification from us with a subject line prefixed with "[RackNerd]..." confirming completion for your service. Our team is continuing to work through the remaining systems in this batch, and we greatly appreciate your patience. UPDATE 4:30 PM PDT: Today’s migration batch remains actively in progress, and our team is continuing to work through the remaining systems at the new facility. A large portion of services have already been restored, and completion notices are continuing to be sent out as individual VPS services come back online. If you have not yet received a separate completion email for your specific VPS, please know that our team is still working through the remaining items in this batch. We appreciate your continued patience as we work to complete the remaining service restorations. UPDATE 7:30 PM PDT: Today’s migration batch has now been fully completed. All services included in the Friday, May 22 migration batch have been brought back online at the new facility. Customers included in today’s batch should have now received a separate completion email from us with a subject line prefixed with “[RackNerd]...” confirming completion for their specific service. We sincerely appreciate everyone’s patience and understanding while our team worked through today’s physical relocation process. This concludes today’s migration batch.

Read the full incident report →

Started May 22, 2026, 08:27 AM UTC· resolved May 22, 2026, 08:27 AM UTC

1. resolved May 22, 2026, 08:27 AM UTC

   We are aware that SJ197KVM 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 May 22, 2026, 04:36 AM UTC· resolved May 22, 2026, 04:36 AM UTC

1. resolved May 22, 2026, 04:36 AM UTC

   We are aware that 7950XCHI302 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 May 22, 2026, 01:13 AM UTC· resolved May 22, 2026, 01:13 AM UTC

1. resolved May 22, 2026, 01:13 AM UTC

   We are aware that DC03LA197KVM 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 May 21, 2026, 05:49 PM UTC· resolved May 21, 2026, 05:49 PM UTC

1. resolved May 21, 2026, 05:49 PM 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 →