All systems are operational

Past Incidents

3rd June 2024

New York Datacenter OUTAGE - 7950XNY300

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

Miami Datacenter Routing Issues with MIA3000 - Shared Hosting Server in Miami

We are aware that our Miami datacenter location is currently experiencing some routing issues, which is causing 100% packet loss when connecting from certain locations. At this time, the routing issue only appears to be affecting one of our shared hosting servers in Miami, which is MIA3000.

Our upstream provider is currently looking into this further and we are awaiting a response from network engineers at this time. Rest assured, we will provide additional updates within this status incident once available.

We appreciate your patience and understanding.

UPDATE: There was a network routing issue between 2 upstream providers, the routing issue has been resolved at this time.

UPDATE: It appears that the routing issues are re-surfacing whereby connecting from some locations result to packet loss (and some do not), please standby while we look into this further with the upstream provider.

UPDATE: This is now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

San Jose Datacenter OUTAGE - SJ201KVM

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

Seattle Datacenter OUTAGE - SEA109KVM

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

2nd June 2024

Los Angeles DC-02 OUTAGE - LAXSSD601nerd1DC02, LAXSSD105nerd1DC02, LAXSSD3014nerd3DC02 & LAXSSD100nerd1DC02

We are aware that LAXSSD601nerd1DC02, LAXSSD105nerd1DC02, LAXSSD3014nerd3DC02 & LAXSSD100nerd1DC02 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: These are now resolved. If you are still experiencing any issues please open a support ticket and we'd be happy to assist.

Los Angeles DC-02 FIBER12 (One Shared/Reseller Hosting Server in Los Angeles DC-02)

We are aware that FIBEr12 (One Shared/Reseller Hosting Server in Los Angeles DC-02) 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.

1st June 2024

New York Datacenter OUTAGE - NYRN189KVM

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

Los Angeles DC-02 OUTAGE - LAXSSD106nerd1DC02

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

Los Angeles DC-02 Outage - LAXSSD7001nerd2DC02

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

31st May 2024

Miami Datacenter Outage - MIA3000 Shared Hosting Server

We are aware that MIA3000 Shared Hosting Server 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.

Seattle Datacenter Outage - SEA117KVM

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

30th May 2024

Miami Datacenter MIA2000 (One Shared/Reseller Hosting Server in Miami)

We are aware that MIA2000 (One Shared/Reseller Hosting Server in Miami) 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.

29th May 2024

San Jose Datacenter Packet Loss in West Coast Datacenters (due to Cogent carrier issues)

We are aware that servers located within our west coast datacenter locations (i.e. San Jose, Los Angeles, Seattle) are experiencing packet loss and/or higher latency than usual for routes traversing through Cogent carrier.

It appears that Cogent, one of our bandwidth providers within the mix is currently experiencing issues in the west coast. This means routes/paths that typically travel through Cogent may be affected.

Just to clarify, this is a wider/widespread issue throughout the US-west coast, and this is not a RackNerd-specific issue. As a prominent carrier, Cogent is a significant part of the Internet infrastructure, and its transit services are used directly or indirectly by many.

Network engineers at our upstream providers are also aware of the incident and are closely evaluating the situation.

UPDATE: The latest updates can be found directly on Cogent’s network status page here: https://ecogent.cogentco.com/network-status

As of now, the latest update from Cogent is:

“Customers transiting our network on the west coast of North America may be experiencing Latency and Packet Loss. This is due to multiple fiber cuts in our vendors network around the Los Angeles area. Our vendors have been contacted and are currently dispatching to further investigate the outage. There is NO ETR at this time. The master case is HD303782528.”

UPDATE: Although Cogent has not marked the issue as resolved on their official status page, we've observed signs of stabilization. To mitigate the situation, our upstream providers have temporarily rerouted traffic away from Cogent routes in certain locations to circumvent the problem. Consequently, if your usual routes tend to prefer passing through Cogent, you might notice slightly higher latency than usual as they may now be taking a different route, though it should not significantly affect accessibility. Additionally, please note that we cannot influence access to external services. If you are accessing external services such as hosted APIs or endpoints that rely on Cogent, these are beyond our control. On our end, we have made every effort to optimize our network to minimize disruptions.

UPDATE: It appears that Cogent has marked this as resolved as there is no longer any mention of it on their status page. Things also appear to be stabilized at this time. We will go ahead and close out this incident.