Dear customers,
A few weeks ago, we removed one memory slot from one of our Dallas servers due to hardware issues. A few months earlier, another Dallas server also experienced RAM-related hardware problems.
We have identified ongoing issues affecting two Dallas nodes and are already working on a solution. We are preparing to either send new memory modules or add a new server to reduce the load on the affected machines.
We appreciate your patience and understanding while we work to resolve this as soon as possible.
Thank you.
Incident reported: 12/10/2026 12:05 pmwe are experiencing hardware instability on Dallas Node 4. To resolve this, emergency maintenance is required to power off the node and remove a defective RAM module. Services hosted on this node may experience temporary downtime. We apologize for the inconvenience and will update this ticket as soon as the node is back online.
Incident reported: 23/09/2026 01:15 pmWe have currently removed the faulty 32GB module and will replace it with a new one at a later time.
we are currently experiencing issues with our Las Vegas servers.
Our engineering team has been notified and is actively investigating the root cause. During this time, services hosted in the Las Vegas location may be unreachable or experiencing degraded performance.
We will post updates on this page as soon as more information is available. No action is required from customers at this time.
We apologize for the inconvenience and appreciate your patience.
Incident reported: 17/09/2026 03:31 amResolved: Network connectivity to our Las Vegas location has been fully restored.
Our upstream network provider has re-announced our IP ranges and we have verified that routing is propagating correctly across external networks. All services at the Las Vegas location are reachable and operating normally.
If you are still experiencing connectivity problems with your service, please open a support ticket and include a traceroute from your location so we can investigate further.
We sincerely apologize for the disruption and thank you for your patience throughout this incident.
Update: Root cause identified — BGP announcement withdrawn by our datacenter provider.
Following the network migration from Los Angeles to Las Vegas, our datacenter provider mistakenly withdrew the BGP announcement for our IP ranges. As a result, our Las Vegas network became unreachable from the global routing table, even though all servers remained fully operational.
The provider has confirmed the error and is re-announcing our prefixes now. Connectivity should be restored shortly, though full propagation across all networks may take a short period of time.
We will confirm here once we have verified that routing is fully restored.
Update: We have escalated this issue to our datacenter provider.
All servers at the Las Vegas location have been verified as physically operational, which points to a network-level issue rather than a hardware failure. The datacenter's network team is currently investigating on their side.
We are awaiting their response and will provide a further update as soon as we receive one. We apologize for the continued disruption and thank you for your patience.
We have identified an issue with our network switch that may cause reduced upload speeds for some customers. Replacing the affected switch is required, and we are currently working to arrange the replacement.
Resolution may take some time. We apologize for the inconvenience and appreciate your patience while we work to restore normal network performance.
Incident reported: 25/08/2026 10:04 amDone
The server migration from the Los Angeles data center to the Las Vegas facility will begin today, July 26, 2026, at 5:00 PM (Los Angeles Time).
Starting at that time, all designated servers and related equipment will be taken offline, decommissioned, and carefully packed for transportation.
The shipment is scheduled to depart on July 27, 2026, with delivery to the Las Vegas data center. During this period, the affected systems will remain unavailable until the migration process is completed and the equipment is installed at the destination.
Updates will be provided as the migration progresses.
Incident reported: 26/07/2026 12:47 pmServer Migration Update – Services Are Back Online
We are pleased to inform you that the datacenter has completed the installation of the servers, and all systems are now online.
If you are still experiencing any issues accessing your VM, please open a support ticket so our team can assist you as quickly as possible.
As previously announced, we will be applying service credits to your account over the next few days. Depending on your account, this may be provided as account credit or as an additional month of service. If your invoice is due soon, we will most likely mark it as paid on your behalf.
We sincerely apologize for the inconvenience caused during this migration and appreciate your patience and understanding.
We will also be publishing a more detailed document explaining the migration process, including why it was necessary and why it was carried out in this manner.
We have an update and the servers will be arriving at the data center in Las Vegas tomorrow, July 31. We hope that the data center will install them immediately on the same day.
The servers have already been dropped off at the UPS Store and are in the process of being shipped to the Las Vegas datacenter.
We have alerted the data center that UPS has not yet picked up the servers, so they can look into the cause of the delay.
The label has been created & UPS may pick up the package by today. Here are the tracking i'd for the package - 1Z0EH8680311056908 & 1Z0EH8680319203690.
We're currently experiencing an issue with the Los Angeles node. It is being reviewed by the datacenter team. We appreciate your understanding and will update you as soon as this is resolved.
Incident reported: 09/07/2026 03:03 amWe wanted to provide you with an update regarding today's service interruption.
All services are now fully operational.
Root cause: The outage was caused by a hardware issue on one of our network switches. We identified a similar issue a few weeks ago and applied a firmware update at the time, expecting it to resolve the underlying cause. However, the issue has recurred, indicating the firmware update was not sufficient to address it.
Resolution: Our team acted promptly to restore service, and all systems are currently stable and operational.
Next steps: Since this issue has recurred despite the previous firmware update, we've determined that a firmware update alone will not provide a permanent fix. We are now evaluating a replacement switch to permanently resolve this issue and prevent future occurrences.
We apologize for any inconvenience this may have caused and appreciate your patience. We'll keep you informed as we move forward with the hardware replacement.
